Hi folks! We're working to compile the C# and VB.NET toolkits using Visual Studio. Currently, we're running Visual Studio 2010 on Windows Server 2003 (with .NET 4.0 installed), and as part of that process are setting the project to be compatible with .NET 2.0. But, what we're finding is that whatever we build runs fine in the Debugger in Visual Studio, but when we try to build a productiion package and run it elsewhere it fails.

So, basically we're looking to see what others' experience has been trying to build this code in Visual Studio 2010. Should it work? Or should we just give up and find a new server or downgrade?

Thanks!

I have it running with every version from 7.0, 7.2, 7.5 and 8.0 running with .NET 2.0, 3.5 and 4.0 with no ill effects. For the most part the CIL is just a wrapper around a bunch of TCP/IP calls so it doesn't depend on language/plaform specific API/PINVOKE stuff that is creates problems. My clients have taken hundreds of thousands of calls with no real problems. I have had to do many fixes around bugs in the CILs themselves but haven't had any problems with .NET. I just updated a client I made with 7.2 and .NET 4.0 last night and it is still running strong. I don't even install the CTIOS toolkit on my devel machines, I just link to the 2 .NET DLLs for whatever version I am using. Of course Cisco doesn't support any of these configs so caveat emptor. But then again their support of custom apps is almost nonexistent anyway so if you think you have the devel chops to support it and understand how it works you can do just about anything you can imagine. The plaform allows a lot of leeway. Good luck and happy coding.
Shannon