Member Avatar for chock

Hi All,

I have a project in VS.Net 2003 (VB.Net). The OS is Vista Ultimate.
The project runs fine without any problem in Vista Ultimate and XP.
I create a setup for my project in Vista it works, but i get a error in a button_click

"Object reference not set to an instance of an object."

in one form which calls dll. This error comes only in Vista in a button click, i am not getting it in XP. Thanks for any help and support.

The button click contains the following code

Dim ObjInfo As New SangEngine.ClsSang
ObjInfo.SubSanghavi(path, DS, IS)

Thanks,
V.Chock

  • 4 Contributors
  • 3 Replies
  • 106 Views
  • 14 Hours Discussion Span
  • Latest Post Latest Post by jbennet

Dani AI

Generated

For : this kind of runtime mismatch after installation is almost always an environment or deployment issue rather than a code bug in the button handler. Differences between running inside the developer machine and running from the installed folder on Vista commonly include missing or unregistered dependencies, file/registry permission problems, and 32/ versus 64‑bit mismatches.

A short diagnostic workflow that usually finds the culprit:

  • Add robust logging around the failing call so you capture the full exception text, stack trace and any InnerException (write to a file so the installed app can report details).
  • Check the Windows Event Viewer for .NET runtime entries and the exact stack trace.
  • Turn on assembly bind logging with the Assembly Binding Log Viewer (Fuslogvw.exe) to detect assemblies that fail to load.
  • Run Process Monitor (Procmon) while reproducing the problem to spot “NAME NOT FOUND” or “ACCESS DENIED” on files and registry keys the DLL tries to open.

Deployment items to verify: the called DLL and any native/COM dependencies are actually present on the target machine and registered; app.config is deployed; required VC++ runtimes are installed; and the app is running with the intended bitness (installing a 32‑bit native DLL on a 64‑bit process will fail silently). Also check any code that assumes the current working directory or writable locations — Vista’s Program Files and virtualization can change behavior.

Tiebacks: and were right to look at environment/privilege differences as a direction; ’s point about modern toolchain updates can help long term, but first collect logs (Fusion/Procmon/Event Viewer) and a minimal repro so the exact missing dependency or permission is identified before changing the build pipeline.

Recommended Answers

All 3 Replies

Member Avatar for Jx_Man

i didn't know cause i never use in vista. but i think you must to download a patch for vista.

Member Avatar for Ramy Mahrous

Try that, right click on your program then run as administrator.. reply if the problem still exists..

Member Avatar for jbennet

use vb 2005. 2003 has major issues with vista

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.