People have been requesting more information about whether my previously mentioned trick to get .NET 3.5 functionality in Windows 2000 works. So far, it mostly seems to be a success although the software is still not being used on a large scale, but I have only found 1 real problem… When I made a WCF service client to access a web service, VS.NET created a section in the app.config file. This caused an exception when I loaded the program on the Windows 2000 PCs. However, I removed the section from the config file and hard coded the configuration info for the WCF client and it worked fine!
No related posts.
Tags: .NET, .NET 3.5, .NET 3.5 SP1, 2000, Coding, Dodgy, VB.NET, Windows, Windows 2000, Workarounds