When you build the setup project in Microsoft Visual Studio 2010 you receive the following warning message:
The version of the .NET Framework launch condition ‘.NET Framework 4’ does not match the selected .NET Framework bootstrapper package. Update the .NET Framework launch condition to match the version of the .NET Framework selected in the Prerequisites Dialog Box.
When you add a Setup project to your solution Microsoft Visual Studio 2010 sets two default values that usually don’t match the project settings: prerequisites and launch condition.
These are both set to “.NET Framework 4 Client Profile” and if you set your project’s target framework to “.NET Framework 4” you get the warning message above.
(See the How to solve “The target version of the .NET Framework in the project does not match…” warning message in Microsoft Visual Studio post to handle the problem with the incorrect launch conditions.)
Set the prerequisites to “.NET Framework 4”
- Right click the Setup project,
- Select “Properties”,
- Select the “Release” configuration,
- Click the “Prerequisites…” button,
- Check “.NET Framework 4 (x86 and x64)”,
- Uncheck “.NET Framework 4 Client Profile (x86 and x64)”,
- Click OK,
- Select the “Debug” configuration,
- Repeat steps 4 – 7.
You made a change to a Microsoft SQL Server database table that requires the re-creation of the table you get the following error message when you try to save your changes:
Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can’t be re-created or enabled the option Prevent saving changes that require the table to be re-created.
Microsoft SQL Server Management Studio doesn’t allow the re-creation of the table if the following option is set in the Microsoft SQL Management Studio configuration:
- In the Tools menu select “Options…”,
- On the left pane select “Designers”,
- Uncheck the “Prevent saving changes that require table re-creation” check box.
When you build your Visual Studio solution you get the following error message:
The OutputPath property is not set for project ‘XYZ.csproj’. Please check to make sure that you have specified a valid combination of Configuration and Platform for this project. Configuration=’Debug’ Platform=’AnyCPU’. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Configuration or Platform.
When you add a new project to a Visual Studio solution the IDE many times changes the settings in the Configuration Manager. Visual Studio 2010 adds a new solution platform “x86” and sets the platform of the existing projects to “x86”. It can also remove the projects from the build list and change their build configuration.
- Open the Configuration Manager,
- For all Active solution configurations:
- Set the Active solution platform to “Any CPU”.
- For all projects that have to be included in the build:
- Set the Configuration to “Debug” or “Release” depending on the environment,
- Set the Platform to “Any CPU”,
- Check the “Build” check box.
There is an Open Source Death Star project on Kickstarter proposed by www.gnut.co.uk
They already collected £238,758 for the “project”. 771 people donated £1 or more, and 1,548 donated £10 or more.
£20,000,000 for more detailed plans and enough chicken wire to protect reactor exhaust ports.
£543,000,000,000,000,00 ($850,000,000,000,000,000) to secure full funding for actual construction.
To keep costs lower the entire project will use open source hardware and software.
Risks and challenges
The only risk is the power of the Force.
The main challenge is assuring Kickstarter that this is a joke and not a serious project. As proof, the goal has been set high enough to make successful funding almost impossible.
When you compile a .NET 4.0 C# application the following error message appears:
The type or namespace name … could not be found (are you missing a using directive or an assembly reference?)
There is also a warning message :
The currently targeted framework “.NET Framework,Version=v4.0,Profile=Client” does not include “System.Web, Version=18.104.22.168, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” which the referenced assembly ….dll” depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project.
The project targets the .NET framework 4.0 Client profile, but some functionality in the referenced project is not supported by the Client profile.
Set the Target Framework of you project to “.NET Framework 4.0”
- In the Solution Explorer right click the project and select “Properties”,
- On the “Application” page set the Target Framework to “.NET Framework 4.0”.
Welcome to Pinter.org!
This is a knowledge base for software developers to share ideas on Microsoft .NET, and Web development. My goal is to share my accumulated knowledge with anyone who is interested in information technology and software development.