Where is the .NET Framework Configuration Tool in .NET SDK 3.5(Mscorcfg.msc)?

[Robert Kochem]

Hi,

I have some problems locating .NET Framework Configuration Tool for
configuring an snk as fully trusted. On the PC I want to do this only
the frameworks up to 3.5 were installed therefore I wanted to download
the .Net SDK 2.0 - but the download page said that it is outdated [1],
superseded by the "Windows SDK for Windows Server 2008 and .NET
Framework 3.5". Therefore I downloaded the WebInstaller and installed
all .Net related packages. After installation I wanted to open .NET
Framework Configuration Tool but it is nowhere to find neither in
start menu nor on hard disk. Did Microsoft forget to include it in
the .NET SDK 3.5?

Robert

[1]http://www.microsoft.com/downloads/details.aspx?FamilyID=fe6f2099-
b7b4-4f47-a244-c96d69c35dec&displaylang=en

 

[Norman Yuan]

There isn't .NET Framework 3.5 Configuration Applet as .NET 1.x/2.0.

..NET 3.5 is just .NET 2.0 + SP1 + extra add-on (.NET3.0 SP1+.NET3.5). That
is, .NET2.0 is the major part of so called .NET 3.5 plus something added to
it (WPF, WF, WCF...).

So, you still use .NET 2.0 Configuration Applet (when .NET2.0 SDK
installed), or .NET2.0's CASPOL.exe (when no SDK installed).

 

[Robert Kochem]

Hi Norman.

.NET 3.5 is just .NET 2.0 + SP1 + extra add-on (.NET3.0 SP1+.NET3.5). That
is, .NET2.0 is the major part of so called .NET 3.5 plus something added to
it (WPF, WF, WCF...).

I knew that this applys for the .Net Framework as I wrote this is not
true for the .Net SDK, as the 3.5 SDK does not include the 2.0 SDK.

So, you still use .NET 2.0 Configuration Applet (when .NET2.0 SDK
installed), or .NET2.0's CASPOL.exe (when no SDK installed).

I prefer a GUI version, therefore I installed .NET SDK 2.0 and added
my strong name key as fully trusted - but it did not helped me much as
my application still refuses to work. Looks like Microsoft replaced
the DLL hell with a .Net configuration hell. Can't say which hell is
worse :-(

Robert

 

[Norman Yuan]

Hi Norman.


I knew that this applys for the .Net Framework as I wrote this is not
true for the .Net SDK, as the 3.5 SDK does not include the 2.0 SDK.


I prefer a GUI version, therefore I installed .NET SDK 2.0 and added
my strong name key as fully trusted - but it did not helped me much as
my application still refuses to work. Looks like Microsoft replaced
the DLL hell with a .Net configuration hell. Can't say which hell is
worse :-(

In the regard of .NET configuration tool, the GUI is simply doing the same
thing as you do with command tool CASPOL.exe. It is with .NET2.0 SDK,
installing .NET 3.5 does not have affect on this. No DLL hell here for sure.
If it does not work for you, I can only say that you did not do iy
correctly.