View Issue Details

IDProjectCategoryView StatusLast Update
0024707CommunityOCCT:Samplespublic2014-09-11 11:48
ReporterabvAssigned Toabv 
Status closedResolutionfixed 
PlatformWindowsOSVC++ 2010 
Product Version6.7.0 
Target Version6.7.1Fixed in Version6.7.1 
Summary0024707: Problem building C# sample win VC 10
DescriptionThe problem is reported by the user MichaelBate on dev forum,

When VS projects (originally VC9) are converted to VC10, version of .NET framework in CSharp projects is kept as it is (3.5), while in C++ projects it gets elevated to 4.0 (default for VC10). This causes incompatibility between the projects.

The manual solution is to change option "Target framework" in properties of C# projects (tab "Application") to ".NET Framework 4".

This should be documented, or perhaps some better way to ensure smooth work of samples with different versions of VS exist.
TagsNo tags attached.
Test case number



2014-04-29 13:02

manager   ~0029127

There seem to be no easy way to enforce same setting of Target Framework in C# and C++ projects when they are converted by Visual Studio from older versions. Hence manual correction is necessary, I have added corresponding paragraph to the sample description. Please review, branch CR24707.

Related Changesets

occt: master 66fb4d9a

2014-04-29 06:06:21


Committer: abv Details Diff
0024707: Problem building C# sample win VC 10

Need to check and correct Target Framework in C# projects after conversion to new versions of Visual Studio described in the sample documentation
Affected Issues
mod - samples/CSharp/ Diff File

Issue History

Date Modified Username Field Change
2014-03-10 14:26 abv New Issue
2014-03-10 14:26 abv Assigned To => bugmaster
2014-04-04 19:02 abv Assigned To bugmaster => abv
2014-04-04 19:02 abv Status new => assigned
2014-04-29 13:02 abv Note Added: 0029127
2014-04-29 13:02 abv Assigned To abv => ysn
2014-04-29 13:02 abv Status assigned => resolved
2014-05-05 17:24 abv Changeset attached => occt master 66fb4d9a
2014-05-05 17:24 abv Assigned To ysn => abv
2014-05-05 17:24 abv Status resolved => verified
2014-05-05 17:24 abv Resolution open => fixed
2014-09-11 11:48 bugmaster Status verified => closed
2014-09-11 11:48 bugmaster Fixed in Version => 6.7.1