Hello,

I'm working on an XP-machine (all updates installed). I want to be able to
run an application from a shared drive, for this to work you have to allow
this using the .NET framework configuration utility, I only see this tool
for the 1.1 version of the framework in my Administrative tools, not for the
2.0 version even though this version 2.0 is installed on my system. I have
already reinstalled (repaired) my 2.0 installation using the redistributable
package but no luck. I have also tried to find the MMC snapin on this
machine but I only find it in the folder containing version 1.1 of the
framework.

Where can I find / How do I start the utility mentioned in the subject ?

On my development machine it's in de SDK folder but that's not available on
my client's machine, I don't think I should install the SDK to every client
machine just to get my app running ...

TIA,
Jurjen.

The sad truth is that his tool is now part of the SDK while CASPOL is still
provided as part of the redistributable package.

So your best bet is likely to use caspol.

--
Patrice


"Jurjen de Groot" <Jurjen.de.Groot (AT) xs4all (DOT) nl> a écrit dans le message de
news: uYr1zy9GIHA.3600 (AT) TK2MSFTNGP06 (DOT) phx.gbl...

Hi Patrice,

... or doing some "magic" to use it alone )
http://mygreenpaste.blogspot.com/200...tion-tool.html


Regards, Alex
[TechBlog] http://devkids.blogspot.com



P> The sad truth is that his tool is now part of the SDK while CASPOL is
P> still provided as part of the redistributable package.
P>
P> So your best bet is likely to use caspol.
P>
P> --
P> Patrice
P> "Jurjen de Groot" <Jurjen.de.Groot (AT) xs4all (DOT) nl> a écrit dans le message
P> de news: uYr1zy9GIHA.3600 (AT) TK2MSFTNGP06 (DOT) phx.gbl...
P>

I don't remember what it was, but there was something I needed to do on a
client machine that required one of the configuration tools dropped in 2.0.
I finally resolved it by adding a deployment project to the application that
configured what was needed. Solved the problem but took awhile to figure
out.

You can use the .NET configuration applet (as we already know that only
included in .NET 2.0 SDK) to make CAS configuration and then have to
generate an MSI package, which includes nothing but CAS configuration
policies, and then use domain group policy to deploy the MSI to user
computers in the domain.


"Jim Rand" <jimrand (AT) ix (DOT) netcom.com> wrote