Debugging such an application is not as easy as a normal windows forms application:
- You must wait for an assembly to load, before you can attach a debugger. You cannot put breakpoints in start-up code, such as constructors.
- Internet Explorer has an assembly cache that may mislead you into thinking you are running the latest version when you are running an older version. "gacutil.exe /cdl" will flush the download cache.
- fuslogvw.exe will help you debug assembly loading.
- Microsoft changed the default security policy between .net 1.1 and .net 2.0, requiring you to grant permissions to all needed assemblies on each client. This can be done with an installer.
- You can connect back to the original server but you cannot easily connect to other servers, if you wish to download data dynamically.
http://blogs.msdn.com/andrewdownum/arch ... fault.aspx
http://blogs.msdn.com/andrewdownum/arch ... ction.aspx
http://blogs.msdn.com/andrewdownum/arch ... EHost.aspx
http://blogs.msdn.com/andrewdownum/arch ... gName.aspx
http://www.mastercsharp.com/article.asp ... TopicID=14