Hard Light Productions Forums
Off-Topic Discussion => General Discussion => Topic started by: iamzack on December 31, 2008, 10:49:10 am
-
Change of subject:
wtf is .NET 1.1?
-
Change of subject:
wtf is .NET 1.1?
Continuing in this direction:
No
****ing
Idea
some old ****?
-
Change of subject:
wtf is .NET 1.1?
Continuing in this direction:
No
****ing
Idea
some old ****?
Nevermind, I found it. It is ****ing old. But apparently I need THIS! EXACT! VERSION! in order to run a certain program. It seems that I was very sloppy in my downloading custom content, and I have a lot of glitchy files. I've located seven that crash the game if they are installed...
Aaaand my modified startup configuration doesn't seem to be working. x.x
*sigh*
So much troubles.
-
http://www.simwardrobe.com/
-
meh. i prefer modthesims2.com
-
I've used them both, but the SimWardrobe webmaster is more a programmer. Plenty of CC from his site.
-
Change of subject:
wtf is .NET 1.1?
Continuing in this direction:
No
****ing
Idea
some old ****?
Nevermind, I found it. It is ****ing old. But apparently I need THIS! EXACT! VERSION! in order to run a certain program. It seems that I was very sloppy in my downloading custom content, and I have a lot of glitchy files. I've located seven that crash the game if they are installed...
Aaaand my modified startup configuration doesn't seem to be working. x.x
*sigh*
So much troubles.
I would have thought all newer version of .NET were backwards compatible.
-
Why is .NET important?
-
.NET is a programming framework similar to Java. To run programs made with .NET, you need .NET runtime, just like is the case with Java.
.NET versions however are not backwards compatible, each of them is like its own isolated framework. Which means you need 1.x to run programs made with .NET 1.x and so on. Currently there are three major revisions of .NET, 1.1, 2.0 and 3.0.
However, there is also .NET framework 3.5 which is somewhat of an oddity. It actually contains framework version 2.0 and 3.0 in one and same package with something new tossed on top of them. So, in the end you only need to download and install .NET Framework 1.1 and 3.5 to have .NET compatibility covered. Then visit Windows or Microsoft Update to get updates for them.
Edit: Almost forgot. .NET Framework is also available for OS X and Linux in the form of Mono.
-
There is another fun oddity with .NET
If you write an extensible architecture you've got to make sure that everything is written in the same version of the CLR
http://blogs.msdn.com/oldnewthing/archive/2006/12/18/1317290.aspx (http://blogs.msdn.com/oldnewthing/archive/2006/12/18/1317290.aspx)
This can cause problems if you don't realise what is going on
The link in the article goes to an MSDN forum (bloody slow) with the following comment from Jesse Kaplan:
Unfortunately unmanaged C++ is really the only way to go here.
Writing in-process \shell extensions in managed code is actually a very dangerous thing to do because it has the effect of injecting your managed code (and the .NET Framework) into every application on the machine that has a file open dialog.
The problems occur because only one version of the .NET Framework can be loaded in a process at any given time (other shared components such as java and msxml have the same property and thus the same restriction).
If you write your shell extension using the 2.0 .NET Framework and an application built with the 1.1 .NET Framework uses a file open dialog, your shell extension will fail because it can not run on an earlier version. Things can get even worse if your shell-extension manages to get loaded in a process before another applications managed code does: your extension may force an existing application onto a different runtime version than the one it was expecting and cause it to fail.
Because of these problems we strongly recomend against using any single-instance-per-process runtime or library (such as the .NET Framework, java, or msxml) in an in-process shell extension.