This is an issue for me currently . It might have to with the security
settings of the local machine.
Unfortunately the c++ complier cannot produce "verifiable" assemblies. The
clr performs this check during JIT compilation. Verification is required by
default for most zones. This I think is a good thing.
Anyway depending on where you are loading your control from ( internet,
intranet, etc. ) you will have to increase the security settings to full
trust. You can perform this task using the .NET configuration tools.
NOTE: I understand that there is a way to set the policy for a single
assembly but I have not had any luck with it so far. What I am suggesting
will open up the door for ALL assemblies to run pretty much unrestricted. It
will, however, allow you to develop your control until a proper solution is
found. I guess what I am trying to say is that this will need to be fixed
before deploying your control into production.
Hope this helps somewhat.
George Economos
> Hi Gary,
>
[quoted text clipped - 5 lines]
>
> <object id=TestControl
classid=http:WindowsControlLibrary1.dll#WindowsControlLibrary1.UserControl1
> height=480 width=640 VIEWASTEXT>
>
> In managed C++ the naming I think I need would be:
> <object id=TestControl
classid=http:WindowsControlLibrary1.dll#WindowsControlLibrary1::UserControl1
> height=480 width=640 VIEWASTEXT>
>
[quoted text clipped - 33 lines]
> rights.
> > --------------------
Thanks for replying. I'm thinking that I may be better off waiting until
the managed C++ overhaul in VS2005, presumably it will fix this? The
production environment is over 2000 desktops, so I would prefer not to have
an upgrade that could potentially cause security issues.
> This is an issue for me currently . It might have to with the security
> settings of the local machine.
[quoted text clipped - 28 lines]
> >
> > <object id=TestControl
classid=http:WindowsControlLibrary1.dll#WindowsControlLibrary1.UserControl1
> > height=480 width=640 VIEWASTEXT>
> >
> > In managed C++ the naming I think I need would be:
> > <object id=TestControl
classid=http:WindowsControlLibrary1.dll#WindowsControlLibrary1::UserControl1
> > height=480 width=640 VIEWASTEXT>
> >
[quoted text clipped - 35 lines]
> > rights.
> > > --------------------
"Gary Chang" - 29 Jun 2004 04:19 GMT
Hi Paul,
Thanks for your quickly response!
> ... I'm thinking that I may be better off waiting until
> the managed C++ overhaul in VS2005, presumably it will fix this?The
> production environment is over 2000 desktops, so I would prefer not to have
> an upgrade that could potentially cause security issues.
We do understand your concern on this scenario, it really would bring some
troubles to the MC++ developers. We will pass your feedback to VC dev team.
Thanks for your understanding!
Best regards,
Gary Chang
Microsoft Online Partner Support

Signature
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------