Unwanted .Net framework dependency

Somehow my application has developed a dependency on the .Net framework.



It is a C++ app built much the same as one would have with Visual Studio 6.



We were happily using Visual Studio .Net 2003 with no dependency on the .Net
framework. Somewhere along the line someone must have accidentally clicked
were they shouldn't have and the dependency arose.



Does anyone have any clues as to where to start to look to remove this
dependency?



Many regards,



Harry Hanley



NOSPAMharry.hanley@xxxxxxxxx



(remove NOSPAM to reply)


.

Relevant Pages

  • Re: .NET Framework 2.0 component
    ... If the previous version did not have this dependency relationship then it was probably a bug. ... Were you ever able to use ASP.net when .net framework feature was *not* in your previous runtime? ... Check out the Embedded team blog: http://blogs.msdn.com/embedded/ ... The blog article refers to a macro component you can download, ...
    (microsoft.public.windowsxp.embedded)
  • Re: .Net 1.1 and MinLogon
    ... You can add .NET Framework in TD configuration and then do the dependency ... Choose MinLogon and run the dependency check again. ... the .Net Framework 1.1 has a dependency on WinLogon> which also brings in Session Manager which conflicts with> MinLogon. ...
    (microsoft.public.windowsxp.embedded)
  • Re: .NET Framework 2.0 component
    ... When I'm doing a check dependency, ... The blog article refers to a macro component you can download, ... I only have .NET Framework 1.1 component. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Use of MinLogon with user accounts and other issues
    ... Basically if you try to put the .NET Framework ... resolved you will come up with an image like the MiniLogon. ... I am assuming that this dependency is only ... > for security reasons we cannot include in our image. ...
    (microsoft.public.windowsxp.embedded)
  • Re: Unwanted .Net framework dependency
    ... > Somehow my application has developed a dependency on the .Net framework. ... > It is a C++ app built much the same as one would have with Visual Studio ...
    (microsoft.public.dotnet.framework)