Member Avatar for karthik_cud

Hello everyone ,im a new guy to vb.net ,i've installed .net2003 in my system , i have a problem with it ,when i click new projects in the file menu , it quits out to the desktop ,i really need ur help .....
.............. karthik

  • 4 Contributors
  • 3 Replies
  • 110 Views
  • 4 Days Discussion Span
  • Latest Post Latest Post by Gold dragon

Dani AI

Generated

This is a real IDE crash (clicking File → New → Project causes Visual Studio to quit), not just a code error in one of your projects. As reported no dialog, start by collecting the crash evidence that Windows records so the root cause can be identified. asked about exceptions; the Application event log is where the IDE records the faulting module name and exception code.

Reproduce the crash and immediately check Event Viewer (Application log) for the entry at that timestamp. Note the faulting application (usually devenv.exe), the faulting module (DLL name) and the exception code — these three values point strongly at whether the problem is Visual Studio itself, the .NET runtime, or a third-party component. Next isolate per-user configuration and extensions: run the IDE from a fresh Windows user profile or temporarily rename the Visual Studio per-user settings folder so the IDE recreates defaults (Windows XP/older: the VisualStudio folder under Application Data; on newer Windows it is under AppData\Roaming).

The New Project dialog reads templates and COM/managed add-ins; corrupted templates or an add-in can crash the dialog. Temporarily move project/item template caches and disable any source-control or third-party add-ins so the dialog loads only built-in templates. Also suspend antivirus/shell-extension utilities when testing — they sometimes hook file dialogs and cause crashes.

Since and raised install issues, verify the IDE and .NET runtime have the latest service packs and updates for their versions (Visual Studio 2003 / .NET 1.1 era updates). If event-log details point to a vendor DLL, update or remove that component. If the faulting module is a Visual Studio core DLL and all isolation tests fail, a repair of the installation can be considered as a last resort.

Recommended Answers

All 3 Replies

Member Avatar for Ramy Mahrous

No exception raises? or send and don't send message appears?

Member Avatar for regcure

It could be that the .Net has not been installed properly, or it could also be due to insufficient memory.

Member Avatar for Gold dragon

Maybe try reinstalling .net2003

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.