Well
I had very hard three weeks with new generation certifications. I received promo codes for beta exams for .NET 2.0 and I was eager to schedule and attend them.
I made a simple calculation that says for period Sept 2001 – January 2006 I took 8 exams and I earned three certifications:
MCP
MCSD for VS 6.0 (which is old now)
MCAD
MCSD for VS .NET ( 2003 )
For last three weeks I was very very active as I went on 4 exams J
These are: as follows:
Exam 71-547 Pro - Designing and Developing Web-based Applications by Using the Microsoft .NET Framework
Exam 71-548 Pro - Designing and Developing Windows-based Applications by Using the Microsoft .NET Framework
MCSD Exam 71-553 - Upgrade: MCSD Microsoft .NET Skills to MCPD Enterprise
Application Developer by Using the Microsoft .NET Framework - Part 1
MCSD Exam 71-554 - Upgrade: MCSD Microsoft .NET Skills to MCPD Enterprise
Application Developer by Using the Microsoft .NET Framework - Part 2
There is one more dev exam I could attend but I am very exhausted.
These exams have been different that I expected but whatever… I am existed and I am looking forward to three relaxing days in Chepelare. I will post pictures when we are back here. I hope we wont have problems with traveling in deep snow and we will beck on time J
This is driving me crazy. Fortunately this time I located error more easily.
Looking at error logs gave me direction about. Error message was:
It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process.
so everything was fine when I created new Application pool for sites using .NET 1.1 and another for .NET 2.0 sites and problem was fixed
We've found a terrible problem while developing websites with ASP.NET 1.1. Initially I though it is version problem because I have .NET Framework 2.0 installed on development machine.
I found an forum post where they said everything is fine when ASPNET account is in Administrators group. But this is nonsense - ASPNET accout CANNOT BE IN ADMINISTRATORS group. Otherwise this will be BIG security hole.
So I kept looking for solution and found article on MS Knowledge base - Process and request identity in ASP.NET:
Blindly grating rights described in section Default permissions for the ASPNET account didn't help us a lot.
I did the following.
- Delete ASPNET account from development machine.
- Execute from Visual Studio .NET 2003 Command Prompt aspnet_regiis -i so ASPNET 1.1 is installed on system and ASPNET accoutn is created.
- Grant read rights for ASPNET on %sysroot%\Windows
- Grant full rights for ASPNET on %installroot%\ASP.NET Temporary Files
- Grant read rights for ASPNET on IIS Web project folder so ASPNET can read root web.config file
- Grant read rights for ASPNET on virtual folder where project reside
- Execute iisreset from command prompt.
This resolve the problem. I hope this helps.
Today I installed .NET Framework Redist 2.0 onthe server. I am very excited about this. I waste about 3 hours on moving one ASP.NET project to ASP.NET 2.0 and at the end I wanted to place it on server so we could evaluate speed. And I got error. Can you imagine?
Then I did some googleing and I found this article which says:
You can configure individual virtual directories in the IIS to use different version. The IIS Management Console has a new tab called ASP.NET, see image below, in which you can select which version you would like to use, whithout doing a lot of script-mappings.

This makes it really easy to make new applications take usage of the new .NET Framework while your old applications still use the .NET 1.1.
I've just finished the setup of the new room in the office. I bought new LCD monitors and two brand new PC which are extremely fast:
Motherboard |
ASUS P5LD2-VM/LGA775/945G/DDR2 |
CPU |
P4 3.2G/FSB 800MHZ/1M BOX |
RAM |
2GB DDR II 533 KINGSTON |
HDD |
160GB SEAGATE 7200/8MB CACHE |
FDD |
1.44 MB TEAC |
VC |
GB RADEON 9600XT/128M/TVO/DVI |
Mouse |
LOGITECH S96 OPTICAL/BLACK |
keyboard |
LOGITECH |
Optical |
DVD-RW LG 4163 |
Case |
3GTS001 /FSP 400W PFC foxconn |
well I am very excited and only thing I have to do is recruiting one Senior .NET Developer and one Junior .NET developer for the office. I hope we will finish recruiting process until Oct 20th
I keep running into this problem - everytime I install my machine (which is not very often) I have to setup remote debugging. th emain problem is that I forgot steps for setup.
I will try to put them here (client computer only - one with VS.NET)
1. At a command prompt, type dcomcnfg, and then press ENTER. Component Services opens.
2. In Component Services, expand Component Services, expand Computers, and then expand My Computer.
3. On the toolbar, click the Configure My Computer button. The My Computer dialog box appears.
4. In the My Computer dialog box, click the COM Security tab.
5. Under Access Permission, click Edit Limits. The Access Permission dialog box appears.
6. Under Group or user names, click ANONYMOUS LOGON.
7. Under Permissions for ANONYMOUS LOGON, select the Remote Access check box, and then click OK.
Restart machine.
Note: I do this in PC behind firewall so WinXP SP2 firewall is stopped.If you need to run debugging with firewall see this http://support.microsoft.com/kb/833977/
today I met very strange issue: website wroks well on local machine and test server but on production server all buttons stopped firing click event.
I did some googleing and found this article on http://geekswithblogs.net/ranganh/archive/2005/04/25/37630.aspx
You may be unable to see the button click events firing on certain machines though it may work in some other machines.
Mostly when you are developing in your local system, the events do work well. But once you move the code to production, the button click events may not fire at all.
This might rise after you install the Microsoft .NET Framework Service Pack 1, which will stop the PostBack Events on client side validation.
To resolve this issue, the aspnet_client folder needs to be reinstalled. To do that type the following from command prompt:-
%windir%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -c
This should resolve the issue.
The above command applies to .NET Framework version 1.1. For 1.0, you need to change the version to v1.0.3705 in the above command.
Thanks you Harish Ranganathan!
I came over very interesting site about job intereview tips
http://sevendeadlysins.theladders.com/
take a look at it - I found it very interesting and confirming my opinion that serious and reliable guys are very rare race.