2) Check for these settings in your Application Pool (inside IIS)
3) Have the following entries in the web.config
Please note that these settings are for Development Enviroment only and not for Production.
4) Adding an extra string in Custom SD entry in the Event Log. This last option however didn’t work for me.
After a fresh install of Windows 7 my ability to update Event Log seems to have changed. I had to go to Inetpub –> right click on website select Authentication –> disable Anonymous authentication and enable Windows Authentication. And now I can write to Event Log just fine
I was debugging a .NET 3.5 app and below is the error message I got when I tried to stop debugging. Have fun!
Humorous Bug in Visual Studio 2008 (Windows 7)
Sometimes when we right click an edmx file and select update model it doesnt do that.
This could be due to a cache problem with the studio. I suggest 2 tips.
a) rename the model connection name to clear cache.
b) close and reopen the visual studio again so that it works. The second tip especially works when the Designer.cs files are empty without any lines of code (which is rather weird).
Hope this helps!
VJ Koganti
When having WCF and ASP.NET website in two different project debugging could become tricky especially if you have just installed windows 7. Here are some tips and tricks that you need to follow:
1) both projects use the same application pool
2) in web.config of both projects make sure you have the compilation property set to true. for ex:
3) Delete the bin and obj folders. Ensure that your bin folder doesnt have a “read-only” turned on for both projects in your solution.
4) Right click on the WCF project. Select properties and then click on the tab that says “WCF Options”. Uncheck the checkbox that has the text: “Start WCF Service Host when debugging another project in the same solution”. This is because this sets up a separate process for the debugging. And the process that your visual studio uses then cannot jump onto the back of this process!
5) Run the application using F5. Then click Debug-> attach to process and select the w3p.exe process.
VJ Koganti