.NET release problem HELP

[Nemok]

I have a serrious problem.I've developed an application on VC6 that used to work fine. Now I have converted it on VC.NET 7.0 and builded in RELEASE configuration. The problem is that it only works on my computer. On other computers that don't have VC installed it just doesn't start. If started with depends.exe (XP Support Tools) it gives the following error: Second chance exception 0xC00000005 (Access violation) occured in "NTDLL.DLL" at address 0x77F8243D Exited "program" with code 128(0x80) They have all the necesary dlls. What should I do? I'm disperate. If there is an error in program why does it work on my computer fine, and on other computers without VC .NET installed crashes without any errors?? Contact: nemoprod@go.ro, www.nemoprod.go.ro .

[bneacetp]

Just a wild guess. If you have the /clr switch turned on (that is you are using .NET in your VC++.NET project) do you have the .NET Framework installed on the other computers that you have been testing your program on? Happy Programming and God Bless! Internet::WWW::CodeProject::bneacetp

[Nemok]

I've reinstalled Windows on my computer and then installed VS.NET 7.0 and the program isn't working on my computer either now. I have the .NET framework installed on my computer.When i try to debug it I receive this error: "Unhandled exception at 0x77f60b6f in nMonitor.exe: 0xC0000005: Access violation writing location 0x00030fdc."In the call stack it shows:" ntdll.dll!77f60b6f() " Somebody help. This is strange.

[bneacetp]

Have you tried the "Clean Solution" option in VC++.NET? That will delete all object files and allow you to perform a completely fresh build. See what that does, and let me know. Happy Programming and God Bless! Internet::WWW::CodeProject::bneacetp

[Mike Dimmick]

Get the Debugging Tools for Windows[^]. From here, you can use WinDbg to debug the process, which if you set it to use Microsoft's Symbol Server[^], will download the operating system's debugging symbols as DLLs are loaded. This should help you see which function in NTDLL is causing the crash and what the call stack is. If you don't want to install this on the system that's having the problem, you can set up VS.NET for remote debugging (follow the instructions on VS.NET CD 1) and use the symbol server from VS.NET. See Microsoft KB article 319037[^]. Stability. What an interesting concept. -- Chris Maunder