Each time i create a new Code Group with the '.Net Framework 2.0 Configuration' utility, it is name 'Copy of XXX' instead of 'XXX'.
I tried to reset all my security policies, but it didn't changed anything...
When i try the 'Evaluate Assembly' command on one of my assemblies (after having created a new code group), the 'Evaluate Assembly' crash ...
Anyone have an idea
Thanks. Ben

New 'Code group' is named 'Copy of XXX' ???
milsdm
I think i found the guilty :) it's the OpenFileDialog component on my form ...
One easy way to reproduce the problem is to create a new VB.net windows forms project, and add an openfiledialog component on the form.
Then, in the 'My Project' window, use the ClickOnce Security Settings (set it to 'Local Intranet' for example), and run the app...
The strange thing is that under .Net v1.1, i could use those dialog boxes without problem, only a real read or write caused an exception ...
But, even if a do a 'calculate permission' within the ClickOnce tab, it doesn't detect the need for 'FileIoPermission' ... So it's strange anyway ! :\
Abill
Yep, that's what i discovered too
while testing it a little bit deeper ...
Anyway, thanks for helping and sharing infos.
LaserGecko
poekid88
tpaxatb
First i created a small Windows App (kinda Notepad) , nothing special here, i'm just using the 'My' namespace for reading and writing text files.
I put the exe on a network share '\\hoth\LabSessions'. Since it's on a network share i expect the app to be unable to read or write on my local drive, but it should at least display it's main window.. But in fact, the app even refuse to launch, it crash at the beginning (securityexception , fileioexception ...), on the 'Application.Run (New frmMyNotepad())' line ...
I believe that while the clr attempts to read the metadata for the class inside the exe it can't... (that's strange, the same app under framework 1.1 loaded perfectly and displayed the main window, it only caused an exception when attempting to read or write a file, that's the expected behavior...)... I tried to reset the security policies of all level, but it didn't help ... I seems that it acts as if the 'Intranet_Same_Directory_Access' code group didn't exists
So, that's why i tried to create i new code group, under the 'Local intranet' code group. I named it 'Test' (displayed as 'Copy of Test') and used the Hash code of my exe, and granted 'Full trust'.
Now, the exe load and run as expected, with full trust. When i try to do an 'Evaluate Assembly' inside mscorcfg, (using the '\\hoth\LabSessions\MyNotepad.exe' path) it crash the MMC ...
Very, very strange indeed ...
Randy Beckwith
Could you please provide the complete exception details (including call stack listing) as returned from its ToString method
I can repro the crash, but only when using hash evidence, so it apparently isn't caused (only) by the "copy of" naming. The problem is probably worth reporting at http://lab.msdn.microsoft.com/productfeedback...