Sukhvinder

The configuration tool is not part of the .NET 2.0 runtime package.

When a user installs the .NET 2.0 runtime package IN ORDER TO RUN A PROGRAM written using .NET 2.0, that USER would need to use the configuration tool in order to trust the assembly that he is planning to run.

The configuration tool should NOT be a part of the SDK; it should be part of the .NET 2.0 runtime package. I tried installing .Net 3.0 Runtime Package and still was not able to get configuration tool and i won't like a user to install 350+ MB of SDK to use my DLL.

Can anyone suggest on how i can override this problem.



Re: .NET Framework Setup Configuration tool is not part of the .NET 2.0 runtime package.

Gabriel Lozano-Moran

This has changed from the installer for the .NET Framework 1.0 and 1.1 because regular users should not use this configuration tool (according to MSFT). You can always use the Code Access Security Policy Tool (caspol.exe) to set trust levels for an assembly in a custom action in your installer or run it from a batch file, script ... . As far as I know plans are to re-add the configuration tool in the next release of the .NET Framework (propably v3.5) by the end of 2007. So there is no need to install the SDK.






Re: .NET Framework Setup Configuration tool is not part of the .NET 2.0 runtime package.

irekpias

Hi.

I must remember my Micro$oft Passport to login and reply.

Are you kidding about don't include graphic tool to manage security settings in .Net 2.0 like in .Net 1.x You Microsoft people teach us to use GUI for task with your OS, but you resign from handy GUI tool for manage security things in .NET 2.0 - "Users shouldn't use this
configuration tool ..." - It's silly for me.

I spent 2 days - no succes as yet - trying to run .NET 2.0 application from network share and play with caspol.exe :/

With .NET 1.x i have nice gui tool - few seconds and permission was granted !

I don't understand, why this handy tool isn't part of .NET 2.0

IT'S BIG MISTAKE AND
INCONSISTENCY !

Ireneusz Piasecki








Re: .NET Framework Setup Configuration tool is not part of the .NET 2.0 runtime package.

MehmetG

I could not find any solution other than below. But at least it works.

There is a way to create an msi file for changing client security options. So you change your computer's settings, then create the msi file and run it on the clients.

Check the article msdn:

.NET Framework Developer's Guide 
Deploying Security Policy

In mscorcfg.msc of 2.0, on Actions menu you will find Create Deoployment Package. You can create a package for Machine Policy of your computer. The output msi file then can be installed on the client. It is fast and easy.

Note that menu items in mscorcfg.msc are only shown when you are on Runtime Security Policy item.

Also note that copying mscordfg.msc and .dll onto client computer, simply did not work. It gave a snap-in error. You can find it in some forums.

 






Re: .NET Framework Setup Configuration tool is not part of the .NET 2.0 runtime package.

Aaron Stebner

There has also been some discussion of this topic on my blog post at http://blogs.msdn.com/astebner/archive/2006/01/23/516671.aspx that might be interesting for folks concerned about this scenario to read. The best way to make sure that Microsoft hears your feedback regarding this type of issue is to report issues or vote on existing issues on the Microsoft Product Feedback Site - http://connect.microsoft.com/site/sitehome.aspx SiteID=210.

Thanks! Aaron