[2005] Run the DB with VB Forms Directly from the Cd

Printable View

Dec 16th, 2007, 02:40 AM
Al-Naib

[2005] Run the DB with VB Forms Directly from the Cd

Hi
I was traing to do application (DB) using access DataBase
with a VB.net forms and run it directly from the CD
is it posible or not
notes:all the queries will be only using the 'select' keywords
i'm glade to here any tips commets or advices
thanks
Dec 16th, 2007, 03:10 AM
jmcilhinney

Re: [2005] Run the DB with VB Forms Directly from the Cd

You can run a VB.NET app off a CD and you can query an Access database on a CD. You will, of course, require the machine running the app to have the .NET Framework and Jet OLEDB driver installed.
Dec 16th, 2007, 03:21 AM
Al-Naib

Re: [2005] Run the DB with VB Forms Directly from the Cd

aha ...
what if i use one of the programms that give the ability to convert
any programm to a portable version , i think it would be an easy way
to ignore the need to the .NetFrameWork
what do you think
Dec 16th, 2007, 03:33 AM
jmcilhinney

Re: [2005] Run the DB with VB Forms Directly from the Cd

I think that if you run a .NET executable then it requires the .NET Framework and if you run a native executable then it doesn't. What do you think?
Dec 16th, 2007, 03:44 AM
Al-Naib

Re: [2005] Run the DB with VB Forms Directly from the Cd

???
what do you mean by a (native executable)
i think this kind of applications ( Convert to Portable ) convert any application
regard the language , i'm not sure but it suppose to work like that
..
Dec 16th, 2007, 04:03 AM
jmcilhinney

Re: [2005] Run the DB with VB Forms Directly from the Cd

A native executable is an executable in native Windows machine code, which a .NET assembly is not. A .NET assembly has a native code header that invokes the Framework, which then reads and executes the MSIL code contained in the assembly. A native executable is pure Windows machine code. These tools you're talking about compile a .NET assembly or whatever into a native executable. It no longer depends on the .NET Framework so it's no longer a .NET application.
Jan 5th, 2009, 08:58 PM
excelthoughts

Re: [2005] Run the DB with VB Forms Directly from the Cd

Quote:

Originally Posted by jmcilhinney

You can run a VB.NET app off a CD and you can query an Access database on a CD. You will, of course, require the machine running the app to have the .NET Framework and Jet OLEDB driver installed.

Sorry to jump in on an old thread, but I thought it was relevant to my question. I am trying to run a .NET 2.0 EXE from a CD, and I get the message "MyEXE.EXE has encountered a problem and needs to close".

.NET 2.0 Framework is installed on the computer.
EXE runs fine if it is run from the hard drive.

Is it because of the app trying to write to a readonly MyEXE.EXE.config file, or that the app is attempting to write to a readonly log file? Is there some setting in Visual Studio that I can set that will allow .NET EXE to run from CD without failing.

Regards
Andrew
Jan 5th, 2009, 09:39 PM
jmcilhinney

Re: [2005] Run the DB with VB Forms Directly from the Cd

Quote:

Originally Posted by excelthoughts

Sorry to jump in on an old thread, but I thought it was relevant to my question. I am trying to run a .NET 2.0 EXE from a CD, and I get the message "MyEXE.EXE has encountered a problem and needs to close".

.NET 2.0 Framework is installed on the computer.
EXE runs fine if it is run from the hard drive.

Is it because of the app trying to write to a readonly MyEXE.EXE.config file, or that the app is attempting to write to a readonly log file? Is there some setting in Visual Studio that I can set that will allow .NET EXE to run from CD without failing.

Regards
Andrew

As I have already stated, a .NET EXE CAN run from a CD without failing. If it's trying to write to a file on the CD then that's your code doing it, not something inherent in .NET applications. Perhaps you need to add some exception handling to your app to see what the actual problem is. You should ALWAYS handle the UnhandledException event of the application to provide a global exception handler. That should catch your exception so you can see the details, plus it will let you shut down gracefully.