I have an application that I distributed to a windows 2000 server machine with only the .net runtime on it. The application would not even start. I created a quick form program with a label where the text was just "Hi". Built the installation, installed it on the server and it wouldn't start. I downloaded the .NET SDK to the windows 2k machine, installed it and the aplications ran fine. What am I missing in the installation build that would cause this to happen
.NET Runtime
Hot Topic
- Resource editor suggestion?
- Security problem
- Excel and SQL Server
- Consuming object arrays in Web Services
- Trying to run Win app over the network throws error.
- App.config problem
- Miltiply applications memory use
- Client requires callbacks
- MSMQ Serializable Hashtable subclass causes a hang when extracting Message.Body
- Convert Integer value to byte Array
.NET Development
- custom marshalling of System::Object* to VARIANT and back again in IJW assembly
- Populating A Combobox
- Nd open source program to detect signal stg of an access point link with wireless client
- Threading Problem
- Checking internet connection
- Com+ object needs to restart machine every time ?
- How to use FtpWebRequest to send FTP MDTM Command to keep origianl timestamp of uploaded file
- Passing a ascii byte array as System.String to a COM BSTR param
- DataSet Location
- AWhy Does Deleted Rows Keep Coming Back?
.NET Runtime
jadog
David,
Thanks for the reply. I am not running with a network path and I used the link to the 1.1 framework which I am using VS.NET 2003 so that should be OK.
I used the VS install builder so I thought it should have brought everything in.
I thought maybe it was because I was trying to use the Oracle ODP drivers for .NET that something was missing. So that's when I wrote the simple program with a lable with text of "HI". I used the Install builder to distribute this as well.
Neither application would work until I downloaded and installed the SDK on the machine instead of the runtime.
jmatt001
Regards,
Vikram
mevivs
A couple of things I would check:
1. Are you running the application from a network path
2. Are you running the same .NET version on the 2000 machine that the application was compiled on
SilverSmurf
I agree that it general installing the SDK shouldn't affect whether your app runs or not. I don't know exactly what the problem is, but here are some things to check to narrow down the problem:
First, are you sure the .NET runtime is installed properly I.e., do other managed apps work at all Does it help if you uninstall and re-install the .NET framework
It's possible your Main method (or one of your class constructors etc) depends on an assembly that, for whatever reason, isn't available until you install the SDK. This would cause an unhandled exception before the Main method is executed. We need to see what this exception is in order to diagnose the problem. Since installing the SDK (which is normally required for debugging) makes the problem go away, this is a little tricky. I'd suggest you look into using either Visual Studio's Remote Debugging capability, or the CorDbg command-line debugger.
For CorDbg, you should just be able to copy cordbg.exe and msdis140.dll from a machine with the SDK installed onto the machine without the SDK, and then run your application from within CorDbg (use the "run" command). The debugger should break when the exception occurs, and you can see what the message is and where it is coming from (use "where" to get a callstack). If that doesn't make the problem obvious, post the callstack and full exception message here.
I hope this helps,
Rick
ramkim