Home All Groups Group Topic Archive Search About

Strong Name broken?

Author
15 Aug 2005 5:14 PM
RyanW
We have an app that runs on a network drive that has a Strong Name assigned
it it and all dll's.  This app ran flawlessly until a recent windows update
was done and it now no longer works.  If i copy all the files to the local
HD, then it works again.  I think it has to do with the Strong Name but am
not sure.  Has anyone had any problems with recent windows updates and their
..Net apps on network drives? 

Thanks

Ryan

Author
15 Aug 2005 8:31 PM
Dominick Baier [DevelopMentor]
Hello RyanW,

what do you mean with "no longer works" - does it crash / do you see an exception
/ if yes which one - do you have a stack trace a.s.o...

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Show quoteHide quote
> We have an app that runs on a network drive that has a Strong Name
> assigned it it and all dll's.  This app ran flawlessly until a recent
> windows update was done and it now no longer works.  If i copy all the
> files to the local HD, then it works again.  I think it has to do with
> the Strong Name but am not sure.  Has anyone had any problems with
> recent windows updates and their .Net apps on network drives?
>
> Thanks
>
> Ryan
>
Author
15 Aug 2005 9:41 PM
RyanW
Here is the message.  It's odd that if I set the All_Code group under
Machine->Code Groups to be Full Trust it works, but if I take it off it stops
working.  All of my Strong Names are trusted with a FullTrust setting so I
don't understand why they don't work anymore.  Since this error is on a
runtime only computer, the information is pretty crappy.  Is there a setting
I can turn on to give more info?

Common Language Runtime Debugging Services

Application has generated an exception that could not be handled.

Process id=0x704 (1796), Thread id=0x720 (1824).

Click OK to terminate the application.
Click CANCEL to debug the application.

Show quoteHide quote
"Dominick Baier [DevelopMentor]" wrote:

> Hello RyanW,
>
> what do you mean with "no longer works" - does it crash / do you see an exception
> / if yes which one - do you have a stack trace a.s.o...
>
> ---------------------------------------
> Dominick Baier - DevelopMentor
> http://www.leastprivilege.com
>
> > We have an app that runs on a network drive that has a Strong Name
> > assigned it it and all dll's.  This app ran flawlessly until a recent
> > windows update was done and it now no longer works.  If i copy all the
> > files to the local HD, then it works again.  I think it has to do with
> > the Strong Name but am not sure.  Has anyone had any problems with
> > recent windows updates and their .Net apps on network drives?
> >
> > Thanks
> >
> > Ryan
> >
>
>
>
>
Author
16 Aug 2005 7:16 AM
Dominick Baier [DevelopMentor]
Hello RyanW,

Can you build a instrumented version of your app - to get more error information??

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

Show quoteHide quote
> Here is the message.  It's odd that if I set the All_Code group under
> Machine->Code Groups to be Full Trust it works, but if I take it off
> it stops working.  All of my Strong Names are trusted with a FullTrust
> setting so I don't understand why they don't work anymore.  Since this
> error is on a runtime only computer, the information is pretty crappy.
> Is there a setting I can turn on to give more info?
>
> Common Language Runtime Debugging Services
>
> Application has generated an exception that could not be handled.
>
> Process id=0x704 (1796), Thread id=0x720 (1824).
>
> Click OK to terminate the application.
> Click CANCEL to debug the application.
> "Dominick Baier [DevelopMentor]" wrote:
>
>> Hello RyanW,
>>
>> what do you mean with "no longer works" - does it crash / do you see
>> an exception / if yes which one - do you have a stack trace a.s.o...
>>
>> ---------------------------------------
>> Dominick Baier - DevelopMentor
>> http://www.leastprivilege.com
>>> We have an app that runs on a network drive that has a Strong Name
>>> assigned it it and all dll's.  This app ran flawlessly until a
>>> recent windows update was done and it now no longer works.  If i
>>> copy all the files to the local HD, then it works again.  I think it
>>> has to do with the Strong Name but am not sure.  Has anyone had any
>>> problems with recent windows updates and their .Net apps on network
>>> drives?
>>>
>>> Thanks
>>>
>>> Ryan
>>>
Author
17 Aug 2005 5:35 PM
Raymond Yuen
Hi RyanW,

It should be due to the Windows Update packages changed the code access
security policy for the Intranet zone.  I would suggest you create a custom
Permission Set based on the permissions that your application (Dlls) required
and assoicate this permission set to a custom Code Group with evidence based
on the Strong Name of your application.

Raymond

Show quoteHide quote
"Dominick Baier [DevelopMentor]" wrote:

> Hello RyanW,
>
> Can you build a instrumented version of your app - to get more error information??
>
> ---------------------------------------
> Dominick Baier - DevelopMentor
> http://www.leastprivilege.com
>
> > Here is the message.  It's odd that if I set the All_Code group under
> > Machine->Code Groups to be Full Trust it works, but if I take it off
> > it stops working.  All of my Strong Names are trusted with a FullTrust
> > setting so I don't understand why they don't work anymore.  Since this
> > error is on a runtime only computer, the information is pretty crappy.
> > Is there a setting I can turn on to give more info?
> >
> > Common Language Runtime Debugging Services
> >
> > Application has generated an exception that could not be handled.
> >
> > Process id=0x704 (1796), Thread id=0x720 (1824).
> >
> > Click OK to terminate the application.
> > Click CANCEL to debug the application.
> > "Dominick Baier [DevelopMentor]" wrote:
> >
> >> Hello RyanW,
> >>
> >> what do you mean with "no longer works" - does it crash / do you see
> >> an exception / if yes which one - do you have a stack trace a.s.o...
> >>
> >> ---------------------------------------
> >> Dominick Baier - DevelopMentor
> >> http://www.leastprivilege.com
> >>> We have an app that runs on a network drive that has a Strong Name
> >>> assigned it it and all dll's.  This app ran flawlessly until a
> >>> recent windows update was done and it now no longer works.  If i
> >>> copy all the files to the local HD, then it works again.  I think it
> >>> has to do with the Strong Name but am not sure.  Has anyone had any
> >>> problems with recent windows updates and their .Net apps on network
> >>> drives?
> >>>
> >>> Thanks
> >>>
> >>> Ryan
> >>>
>
>
>
>
Author
18 Aug 2005 4:38 PM
RyanW
I did that originally but that is what appears to now be broken.  My String
Name works for some dll's but not all, yet all the dll's use the same key
file.

Show quoteHide quote
"Raymond Yuen" wrote:

> Hi RyanW,
>
> It should be due to the Windows Update packages changed the code access
> security policy for the Intranet zone.  I would suggest you create a custom
> Permission Set based on the permissions that your application (Dlls) required
> and assoicate this permission set to a custom Code Group with evidence based
> on the Strong Name of your application.
>
> Raymond
>
> "Dominick Baier [DevelopMentor]" wrote:
>
> > Hello RyanW,
> >
> > Can you build a instrumented version of your app - to get more error information??
> >
> > ---------------------------------------
> > Dominick Baier - DevelopMentor
> > http://www.leastprivilege.com
> >
> > > Here is the message.  It's odd that if I set the All_Code group under
> > > Machine->Code Groups to be Full Trust it works, but if I take it off
> > > it stops working.  All of my Strong Names are trusted with a FullTrust
> > > setting so I don't understand why they don't work anymore.  Since this
> > > error is on a runtime only computer, the information is pretty crappy.
> > > Is there a setting I can turn on to give more info?
> > >
> > > Common Language Runtime Debugging Services
> > >
> > > Application has generated an exception that could not be handled.
> > >
> > > Process id=0x704 (1796), Thread id=0x720 (1824).
> > >
> > > Click OK to terminate the application.
> > > Click CANCEL to debug the application.
> > > "Dominick Baier [DevelopMentor]" wrote:
> > >
> > >> Hello RyanW,
> > >>
> > >> what do you mean with "no longer works" - does it crash / do you see
> > >> an exception / if yes which one - do you have a stack trace a.s.o...
> > >>
> > >> ---------------------------------------
> > >> Dominick Baier - DevelopMentor
> > >> http://www.leastprivilege.com
> > >>> We have an app that runs on a network drive that has a Strong Name
> > >>> assigned it it and all dll's.  This app ran flawlessly until a
> > >>> recent windows update was done and it now no longer works.  If i
> > >>> copy all the files to the local HD, then it works again.  I think it
> > >>> has to do with the Strong Name but am not sure.  Has anyone had any
> > >>> problems with recent windows updates and their .Net apps on network
> > >>> drives?
> > >>>
> > >>> Thanks
> > >>>
> > >>> Ryan
> > >>>
> >
> >
> >
> >