4

I don't recall any configuration needed on a server needed after installing the .NET frameworks (there are 7 of them now BTW). Having said that, an app is targeted toward a specific framework and not a specific version of VS. It's possible they used VS2010 and targeted the 2.0 framework, etc. When you deploy the apps, you may have to tell IIS which ...


2

Yes they can. No configuration of the .NET Framework should be required.


2

Why are you installing Visual Studio on servers to run your applications? If you compile them properly and install just the necessary Visual Studio runtimes, it will work fine and without the overhead and licensing cost of full VS licenses. You can have two versions of VS installed simultaneously, but this is just a bad bad bad way of doing what you want.


1

The re-distributable for the web server for the version which comes with Visual Studio 2010 can be found downloaded from SAP. These links may go stale, but as of 17-Dec-2011: http://www.sdn.sap.com/irj/sdn/crystalreports-dotnet The heading of the section is "Download Crystal Reports for Visual Studio 2010" under "Knowledge Center" and the link has text "...


1

This could be a symptom of agressive File System Caching. Download RAMMap from Sysinternals to find out what is taking up all this memory As described in the kb article, you need to look for large Available or Standby Memory claims in the "Metafile" usage category:


1

You should know. Is your application 32 bit or 64 bit? You can set this up for VB.NET.... and.... 64 bit makes maybe little sense for most apps (that is the reason there is no 64 bit office in wide use - ms recommends against the use of it unless there is a need, like HUUUUUGH excel sheets). As you say: The target CPU of our VB.NET app is x86. That says ...


1

you could try to : netstat -a and see which connections your trying to make odbcad32.exe or variant to see which connections you have configured .For Windows 2003: %systemdrive%\SysWoW64\Odbcad32.exe or run it from Start\Run


1

You can run a packet capturing application like wireshark (Linux + Windows) or tcpdump (Linux). If your server is busy, it may not be easy to recognize the relevant/irrelevant connections. If you know the port number/protocol, you can write filters to see less traffic.


Only top voted, non community-wiki answers of a minimum length are eligible