D
D.Z. Simpson
Hi all,
Somehow VS2003 CF project handling on my PC got broken, the problem seems to
be that VS no longer knows where to find the CF assemblies.
When creating a new CF project, the References list in the solution explorer
is empty and the project won't compile until I add manually the need
assemblies from the CompactFrameworkSDK folder.
When I open an existing project, created before that problem appeared, I get
a bunch of 'cannot find assembly' messages, and again I must manually add
the assemblies or explicitly set the assembly search path of the project.
Does anyone has an idea how to let VS know where to look for the CF
assemblies, e.g. a registry key or a config file option? Reinstalling Visual
Studio and the .NET Framework and SDKs does not help - I tried that several
times in the last week.
Explicitly setting the CF assembly paths is not an option because the
projects I work on are redistributed as samples with our company's CF
control, and developers that open them later will likely have the CF
installed in a different folder...
Any help will be greatly appreciated.
TIA
Don
Somehow VS2003 CF project handling on my PC got broken, the problem seems to
be that VS no longer knows where to find the CF assemblies.
When creating a new CF project, the References list in the solution explorer
is empty and the project won't compile until I add manually the need
assemblies from the CompactFrameworkSDK folder.
When I open an existing project, created before that problem appeared, I get
a bunch of 'cannot find assembly' messages, and again I must manually add
the assemblies or explicitly set the assembly search path of the project.
Does anyone has an idea how to let VS know where to look for the CF
assemblies, e.g. a registry key or a config file option? Reinstalling Visual
Studio and the .NET Framework and SDKs does not help - I tried that several
times in the last week.
Explicitly setting the CF assembly paths is not an option because the
projects I work on are redistributed as samples with our company's CF
control, and developers that open them later will likely have the CF
installed in a different folder...
Any help will be greatly appreciated.
TIA
Don