Groups | Blog | Home
all groups > dotnet academic > november 2003 >

dotnet academic : MS .NET Framework


Boris Arkenaar
11/30/2003 3:43:09 PM
Hello,

When I create an application with VS .NET 2003 and it
runs properly on that computer. And then I try to run it
on an other computer I get an error at startup and the
application is terminated. The error message follows:
"The application failed to initialize properly
(0xc0000135). Click on OK to teminate the applicaton."
I searched on internet and found that I had to install
the .NET Framework to run the application and it did work
after the installation.

My question is if i can build an application that doesn't
need .NET Application to be installed. Professional
programs also doesn't need it and it is not cool to
install the .NET Framework every time I am on a computer
that doesn't have it installed and want to run my
application, especially when I am on a computer and I
don't have administrator rights to install it.

Thank you in advance.
Ed Kaim [MSFT]
12/1/2003 12:09:54 AM
No, .NET Framework applications require the .NET Framework.

[quoted text, click to view]

Boris Arkenaar
12/1/2003 3:56:24 AM
Can you then tell me how I can create a none .NET
Framework application? Or do I have to use an older
verion of Visual Studio to build a none .NET Framework
application? And maybey thats not worth it.

Thank you in advance,
Boris.
[quoted text, click to view]
Peter van der Goes
12/1/2003 8:19:59 AM

[quoted text, click to view]

Hello, Boris.
If you use the .NET languages (I'm referring to VB.NET and C# here), the
target machine for your applications must have the .NET Framework installed.
You can add the framework as part of your export package, so it installs
automatically as part of your application, if necessary. You can develop C++
applications (using the Windows API or MFC) that do not require the .NET
Framework.
The requirement for the .NET Framework is not that different from that for a
Java Virtual Machine on any computer that runs Java applications or applets.
So, the need for supporting software on the target machine is not new, or
unique to Microsoft. The .NET Framework will be part of future OS versions
from Microsoft, IIRC.

--
Peter - [MVP - .NET Academic]

Evan Freeman[C++ Samuri]
12/4/2003 3:32:35 PM
Peter,

I just want to correct this since this is an academic forum.

"If you use the .NET languages (I'm referring to VB.NET and C# here), the
target machine for your applications must have the .NET Framework
installed."

If you write "managed code" you are required to have the .NET Framework
installed. However you can write unmanaged code(C++ currently only
unmanaged/managed language) that will run on target systems without the .NET
Framework installed.

I also believe you can write unmanaged VB code as well. Though I have yet to
try this so don't quote me on it =]/

-Evan


[quoted text, click to view]

Peter van der Goes
12/5/2003 7:15:33 AM

[quoted text, click to view]
Thanks Evan. I had no idea you could write unmanaged code in VB, and I
should have used that term in my description to be more clear.
Peter - [MVP - .NET Academic]

Ron
12/8/2003 8:20:13 AM

[quoted text, click to view]

Isn't MS dropping VB over VB.NET? I'm sure the MCP exams are discontinued
after June 2004.

Ron

Peter van der Goes
12/8/2003 8:22:55 AM

[quoted text, click to view]
Sorry if I was vague. In the context of the thread subject, I assumed VB
would imply VB.NET. I believe that is what Evan meant as well.

--
Peter - [MVP - .NET Academic]

Evan Freeman[C++ Samuri]
12/9/2003 1:46:25 PM
Actually I mis-spoke myself. MS is discontinuing VB over VB.NET, which to a
VB expert, like myself, very unfortunate. You can still do "unmanaged"
programming of VB with the VB6 compiler, and "managed" with the VB.NET
compiler.

My personal opinion is if you want to write managed code, then use c#. If
you choose to use VB.NET and are an experienced VB programmer, be prepared
for a learning curve as the language has changed quiet a bit.

I think that MS should continue supporting unmanaged VB in the VS.NET IDE
area, as they have with C++. But since MS owns VB I guess it's their choice.
I also suppose since the .NET Framewrok will be included in future releases
of the Windows OS, it is a moot point. But I still like being able to write
code that is not dependent on a framework to be installed, also I have heard
many complaints about running .NET applications on older versions of the
Windows OS (i.e., Win98). Ahh well life goes on, and on, and on ......

-Evan


[quoted text, click to view]

Peter van der Goes
12/9/2003 11:23:09 PM

[quoted text, click to view]
Ah. Thanks for the clarification, Evan.
Now I'll admit to having misinterpreted your earlier comment, in addition to
being vague in my reference. Are things getting more complicated, or am I
just getting old :-)?

Evan Freeman[C++ Samuri]
12/10/2003 11:39:08 AM
I think WE are just getting old. =]p


[quoted text, click to view]

AddThis Social Bookmark Button