[CONNECT C#] Problem Building Example with Viz Studio

Hi Jon,

I tried to compile the example you mentioned in Visual Studio 2015 Professional and no error or warning was reported.

But! I had to modify .cspoj file manually before I was able to compile the project. The problem was that  NET target framework configuration was missing in the file, so at first I received a bunch of errors and warnings, because default version 4.0 was used automatically, which is in conflict with version 4.6.1 that was used to build referenced assemblies.

I added <TargetFrameworkVersion> node to ManagedToolsExample.csproj, so it looks now:

  ...
  <AssemblyName>ManagedToolsExample</AssemblyName>
  <TargetFrameworkVersion>v4.6.1</TargetFrameworkVersion>
  <FileAlignment>512</FileAlignment>
</PropertyGroup>

and the compilation from Visual Studio runs fine.

With regards,

 Jan

Thanks, Jan! That fixed my problem.

I had tried to change the .NET Framework Version in the project properties, but that resulted in an incomprehensible error dialog.

Hi Jon,

it's good to know the problem is solved :-)

Unknown said:

but that resulted in an incomprehensible error dialog.

Yes, from some reasons to change the target framework is not possible, regardless it should work.

With regards,

  Jan

Hi Jon and Jan,

I am able to reproduce the issue as originally stated. Using a make file enforces a policy to assert the correct tool set version and configuration being set. I would believe it to be more safe to not include (at all) specific framework properties in the csxproj; since doing so as you can imagine requires more frequent (manual) updates of the csxproj to compile correctly.

An alternate way to do what Jan correctly suggested would be to set this in your development environment:

set TargetFrameworkVersion=v4.6.1

Doing so will effectively do the same change, affecting all projects that do not have set TargetFrameworkVersion defined. I did see a couple delivered examples that specify specific .NET versions attributes that may need to be sorted out. I suspect the only way you could modify the project properties for the default target framework version would be to ship the vcxproj with a default version property being provided, to not encounter the error you and others have seen and posted about. I will try to identify a better/best practice to ensure proper and supportable compilation; even if the developer shell should perform the dynamic setting of the version identified for TargetFrameworkVersion.

Thank you both!
Bob

Unknown said:

set TargetFrameworkVersion=v4.6.1

Thank, Bob!  That worked OK.

I set it as a Windows environment variable and confirm that it shows up in my Viz Studio project properties.

Please note my comment in the first post about undocumented classes.

Hi Bob,

thanks for the confirmation and explanation of the situation!

Unknown said:

I will try to identify a better/best practice to ensure proper and supportable compilation;

Well, I see pros and cons for both discussed options:

• To define .NET version for in every .csproj file individually will work fine for people that will just start Visual Studio ignoring a fact that Dev Shell is an official development environment. But if the version will change, every project has to be changed individually.
• To define .NET version as a part of environment seems to be system solution, but in such case it has to be explained in readme and Dev Shell configuration has to provide this setting.

So ... what about a compromise solution to use conditional definition?

<TargetFrameworkVersion Condition="'$(TargetFrameworkVersion)' == ''">v4.6.1</TargetFrameworkVersion>

If Visual Studio will be started independently, v4.6.1 will be used, but if started in environment where TargetFrameworkVersion variable is defined already, it will be used, so "target network alternatives" can be tested easily. On the other hand there are not many options where to go from 4.6.1, because 4.6.2 is not supported at Windows 8.0 and 4.7 is still quite new.

With regards,

  Jan

Unknown said:

.NET 4.6.2 is not supported at Windows 8.0

Wikipedia and Microsoft tell us that .NET 4.6.x is available from Windows 7 SP1 and later, including 8.1.  Are you being very precise when you write 8.0?

Unknown said:

Are you being very precise when you write 8.0?

Yes, exactly :-)

.NET Framework 4.6.2 requires Windows 8.1, but if you have Windows 8.0, only 4.6.1 can be used.

This is minor condition, I don't know about any user that have stayed on 8.0 and did not migrate to 8.0, but because of this dependency, when you want to support "Windows 7 SP1 and newer", you should use 4.6.1 and not 4.6.2.

With regards,

  Jan