1 of 1 people found this helpful
There is a procedure for uninstallation that seems to work that is fairly easy to find. I would suspect the Easy5 since I had a bad experience with a partial installation of software. The free part gave an error on every startup and I don't know if the full package had the problem.
I have the Visual Studio uninstall instructions. But, my IT people have gone through the unistall /install cycle several times already. Do you think that would matter, or should I go through the process again with the right procedure? Thanks for the help.
The Guthrie procedure may still be the only one available. If SQL Server is present it should be fully patched. IIS issues are separate and would required a clean install as far as I know (IIS set first).
I'm a hydraulic systems engineer, I don't really know what that means, but I'll try to figure it out. Thanks, again.
It is certainly possible that a Microsoft update is needed for the .NET framework but it is more likely the IVF program is not fully compliant. Corporations such as Hewlett Packard are slow enough complying with the Windows operating systems. Your problem must be more than an annoying message: it's preventing installation. A clean install from OS through the MSC software will likely give the same problem unless the IT department has missed something. Unless you're programming, the Visual Studio program should be irrelevant. If someone in your firm intends to extend the capabilites of the MSC software or augment them with programs, they may have established a pattern that is not compliant. If the program is internet enabled then the IS information services could be a problem. Enabling that through changes in Windows Features is required prior to the installation of Visual Studio if programming is involved. The reverse, through a post-install registry modification may not work for all programs. Certain service packs are required prior to installation of SQL Server and Visual Studio dependent on the order of installation and versions.
You should not need to deal with this since the IT department should be contacting Microsoft or the development network and MSC. Having worked in small firms and divisions I understand it could require your involvement to proceed. I would personally do a clean install: OS and everything else but I use Visual Studio and access MSDN. If you do you should be registered as the owner of Visual Studio rather than the IT, giving you access to more information. Someone should spring for Windows 7 as well, and/or a separate machine. Windows Virtual PC can salvage many old programs. Hope that helps.
I've found a problem I had installing my little test program two years ago. The message involved the global assembly cache. Assuming the reinstallations have not messed up the system it may be possible to install an older .NET version that was targeted by the program. Updates may only relate to the newer version. Better assistance would be found in the microsoft or developer forums.
When I install IVF 11.1, it wants to go into the Program Files (x86), this is also where my license file is. Is this correct for a 64-bit PC, or should they both be in Program Files? Also, here is the MSC Easy5 error message:
Microsoft (R) Incremental Liinker Version 9.00.21022.08
wsock32.lib libifcoremd.lib msvcrt.lib oldnames.lib /nodefaultlib:libcmt.lib /nodefaultlib:msvcrtd.lib
LINK : fatal error LNK1181: cannot open input file 'wsock32.lib'
The x86 location may still be used even in Vista or Windows 7 64-bit. I can't find the .NET framework version info related to audio I noted at one time except in the SDK (software development kit) which should not apply.
I haven't seen anything about wsock32 since dial-up modem days. That suggests your problem is related to the IIS setup. That setup can depend on whether your using Microsoft Server or SQL Server. If you don't use either then there shouldn't be problem unless the install/reinstall of Visual Studio changes corrupted something in the registry. I suspect it would be easier to install without Visual Studio present.
OK I found it. When I had the installation problem the .NET framework 3.5 was present in Windows/Microsoft.NET/Framework64 and Framework but not 3.0 on one computer that lacked Visual Studio. I installed dotnetfx3setup.exe and the test program installed. The audio was garbled and that may have been caused by a short in the speakers. If your application was built on .NET 3.0 they should indicate if that is required.
Part of this was updating from Visual Studio 2005 to 2008. MSC concluded that their new version of Easy5 could not run on a 64 bit PC with VS 2005, an oversight on their part. Somewhere along the troubleshooting line, an IT guy told me to delete MS Framework .NET 2.0 SDK - ENU since it might be associated with older versions. I kept it in the recycle bin and yesterday restored, repaired, and downloaded SP2. This seems to have fixed my problem.
Thanks for the help. I enjoy troubleshooting problems on carbueretors, but not on computers.
Although I had misintrepeted the capabilities of VS2005 myself, I'm sure you're much better off with VS2008. The presence of versions of .NET are somewhat counterintuitive since the idea of it is to eliminate "DLL Hell".