This is odd !
-
i want to distribute my C# app to a win98 platform... i installed the framework 1.1 redist on it and ran that app and this is what i get... " ...some exception... cannot be handled.....[some process value]...[some thread value]..." whats the conventional way of compiling an app to distribute? isnt it simply , setting the mode to release instead of debug and then compile?
-
i want to distribute my C# app to a win98 platform... i installed the framework 1.1 redist on it and ran that app and this is what i get... " ...some exception... cannot be handled.....[some process value]...[some thread value]..." whats the conventional way of compiling an app to distribute? isnt it simply , setting the mode to release instead of debug and then compile?
You can distribute a debug assembly. You just shouldn't. You compile like you normally would. C# compiles to Intermediate Language, which all .NET languages compile to. This is JIT'd into native code and executed on the machine, essentially like Java does. This is a fundamental concept of .NET. Your error message helps none. Changes are you're using a class that only works on Windows NT. If you actually read the documentation as you develop (now there's a concept), the docs state which operating systems are supported. If you can't give us the full details to try to help you, then please don't post. This is as informative as something stupid like, "It doesn't work".
Microsoft MVP, Visual C# My Articles
-
You can distribute a debug assembly. You just shouldn't. You compile like you normally would. C# compiles to Intermediate Language, which all .NET languages compile to. This is JIT'd into native code and executed on the machine, essentially like Java does. This is a fundamental concept of .NET. Your error message helps none. Changes are you're using a class that only works on Windows NT. If you actually read the documentation as you develop (now there's a concept), the docs state which operating systems are supported. If you can't give us the full details to try to help you, then please don't post. This is as informative as something stupid like, "It doesn't work".
Microsoft MVP, Visual C# My Articles
ok ok chill my app cant be specific for NT(or for that matter any other) , coz its just a normal beginner c# app. i have used simple basic XML functions and general GUI stuff, so its nothing complex. but sorry for not informing you. the err goes like , application has generated an exception that cannot be handled.. pid = 0xc70(3184) tid = 0xc78(3192),
-
ok ok chill my app cant be specific for NT(or for that matter any other) , coz its just a normal beginner c# app. i have used simple basic XML functions and general GUI stuff, so its nothing complex. but sorry for not informing you. the err goes like , application has generated an exception that cannot be handled.. pid = 0xc70(3184) tid = 0xc78(3192),
Don't tell me to chill. When you post such an uninformative question, expect a uninformative answer. And yes, even some basic things (or things a beginning might think are basic) can be NT-only, like Opacity. You should understand what types you're using and members your calling. You'd be surprised at how much isn't supported on Windows. This application exception looks more like a win32 exception, which means the .NET Framework isn't installed right. Was your application bult in VS.NET 2002 or 2003? 2002 only compiles for .NET 1.0, and 2003 only compiles for .NET 1.1. If you used the command-line compiler, which version did you use. While the .NET Framework is typically backward- and forward-compatible, it is not always. Did you reboot after installing the framework? Is your app running locally or from across the network? There's code access security to take into account in those cases, although in Windows NT at least the message is different.
Microsoft MVP, Visual C# My Articles
-
Don't tell me to chill. When you post such an uninformative question, expect a uninformative answer. And yes, even some basic things (or things a beginning might think are basic) can be NT-only, like Opacity. You should understand what types you're using and members your calling. You'd be surprised at how much isn't supported on Windows. This application exception looks more like a win32 exception, which means the .NET Framework isn't installed right. Was your application bult in VS.NET 2002 or 2003? 2002 only compiles for .NET 1.0, and 2003 only compiles for .NET 1.1. If you used the command-line compiler, which version did you use. While the .NET Framework is typically backward- and forward-compatible, it is not always. Did you reboot after installing the framework? Is your app running locally or from across the network? There's code access security to take into account in those cases, although in Windows NT at least the message is different.
Microsoft MVP, Visual C# My Articles
-
i want to distribute my C# app to a win98 platform... i installed the framework 1.1 redist on it and ran that app and this is what i get... " ...some exception... cannot be handled.....[some process value]...[some thread value]..." whats the conventional way of compiling an app to distribute? isnt it simply , setting the mode to release instead of debug and then compile?
Ashwin C wrote: " ...some exception... cannot be handled.....[some process value]...[some thread value]..." whats the conventional way of compiling an app to distribute? These errors are a pain in the ass to sort. First, I'd recommend building a default C# wizard generated application. See if that works. At least then you know that .NET is installed correctly on the Win98 machine. If the basic app works, start commenting out code until your's starts working. (Alternativly, put a few MessageBox statements into your code flow and see how far it is getting) You might want to try a Windows update and see if the 98 machine is missing any important updates. Michael But you know when the truth is told, That you can get what you want or you can just get old, Your're going to kick off before you even get halfway through. When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
-
.NET ent architect 2k2 i tried this out on systems running .NET 1.1 and 1.037, same err on both !
VS.NET 2002 builds for .NET 1.0, so make sure that .NET 1.0 (v1.0.3705) is installed. Since you said you did that, make sure you have the same service pack installed as you do on your system (you should have 1.0 sp2 installed). .NET 1.0 has not be released with sp2 included. Finally, since it's Windows you must reboot. Even a few features in .NET require a reboot on Windows NT. It is a system-level component. One other thing you can do (as opposed to using
MessageBox, which is not a viable form of debugging and can't show you near enough) is to install the .NET Framework SDK on the machine and use cordbg.exe to step through a debug build of your application. Heck, for that matter, you can even try compiling your source using csc.exe that comes with the Framework (not the SDK). It will still compile whether certain Types or members are NT-only, but it could help determine if there are other errors when trying to compile your code (not necessarily with your code).Microsoft MVP, Visual C# My Articles
-
i want to distribute my C# app to a win98 platform... i installed the framework 1.1 redist on it and ran that app and this is what i get... " ...some exception... cannot be handled.....[some process value]...[some thread value]..." whats the conventional way of compiling an app to distribute? isnt it simply , setting the mode to release instead of debug and then compile?
Welcome to the .NET world. I have personally dismissed .NET at all for the time being. From the many blocking issues I have had with deployment, I claim that .NET is not ready for prime time. Deal with it. If you want frightening weblog posts from CLR guys, let me know.