Knowledge Base for IT Professionals, Teachers and Astronauts
If you don’t need a folder in the Subversion database anymore follow the the steps below.
If you are using the TortoiseSVN Subversion client
In the repository browser:
Enter a message and click the “OK” button.
If you added the AnkhSVN – Subversion Support for Visual Studio from http://ankhsvn.open.collab.net/ you can easily version your files as you develop them.
In your application there could be projects or folders that you don’t want to include in source control.
To ignore the changes in a project open the Solution Explorer in Visual Studio 2010,
To add items to source control in Microsoft Visual Studio 2012 open the Source Control Explorer and click the “Add Items to Folder” button on the tool bar.
If a folder is selected Visual Studio does not display the new files in the current folder:
To be able to add the new files from the current folder, click somewhere on the background of the file list, so no item is selected, and click the “Add Items to Folder” button again:
When Microsoft releases a new version of Visual Studio developers would like to use the new features of the new IDE. Usually the new version of Visual Studio converts the solution and project files to a new format to be able to save the new settings of that version of the IDE. More seasoned developers already experienced this conversion madness multiple times migrating their applications from VS 2003 to VS 2005 to VS 2008 to VS 2010 and now to VS 2012. Knowing the past we can predict that this trend will continue in the foreseeable future, so it is better to be prepared and set up our applications for easy conversion from the get go.
This post explains how to convert an application from Microsoft Visual Studio 2010 to 2012.
First prepare your application for the conversion. Read the “How to set up Microsoft Visual Studio solutions for easy conversion…” post to get all the details step-by-step.
For every Console Application, Windows Service and Class Library project make a copy of the Project_2010 folder as Project_2012
Remove the read only attribute from the folder and all sub folders and files in it:
Click OK on the next window to remove the read only flag from all files and the sub folders too.
Open the “Project_2012” folder and delete the “bin”, “obj” folders and the “.csproj.vspscc” TFS file.
For Web Applications and Web Services make a copy of the …_2010.csproj web project file as …_2012.csproj and remove the read only attribute from the _2012 version:
In Visual Studio 2012 select “Open”, “File…” from the menu,
Make a copy of the Solution_2010 folder as “Solution_2012”.
Remove the read only flag from the “Setup_2012” folder and its sub folders as you did it with the Project_2012 folder above.
Delete the “.vssscc” file. Visual Studio 2012 cannot work with setup projects, so also delete the “Setup” folder with the VS 2010 setup project in it.
Open the solution file as XML in the “Solution_2012” folder and replace “_2010” with “_2012” as you did it in the Project_2012 file above.
Open the solution in Visual Studio 2012, and click OK on the warning dialog about the Setup project. Visual Studio 2012 does not support the Setup project any more. If you want to create MSI files use WIX to generate them.
To remove the Setup project from the solution right click the setup project and select “Remove”
Make sure all of your projects use the same .NET framework. See the “Yellow exclamation point next to a project reference…” post for more information.
Make a copy of the Config_2010 folder as Config_2012
Modify the App.config files in the Config_2012 folder
If the solution was created in Visual Studio 2008 or an earlier version
<startup><supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/></startup>
If the solution was created in Visual Studio 2010
Modify the Web.config files in the Config_2012 folder
targetFramework="4.5" )controlRenderingCompatibilityVersion="4.0" )
<compilation defaultLanguage="c#" debug="false" targetFramework="4.5" />
<pages controlRenderingCompatibilityVersion="4.0" clientIDMode="AutoID"/>
Microsoft releases a new version of Visual Studio every 2-3 years, but most of the enterprise applications have to be operational for years. Many companies developed applications in earlier versions of Microsoft Visual Studio ( VS 2003, VS 2005, VS 2008, VS 2010, or VS 2012 ) and the developers would like to use the new features of the VS 2013 development environment and the .NET 4.5 or higher Framework, but the conversion looks very hard and time consuming. If the application’s lifespan is long, the projects and solutions could be converted multiple times, so it makes sense to prepare your applications for the easiest migration as soon as possible. Preferably set up all projects and solutions during the initial development phase, so later the conversion will be easy and straightforward.
You can set up your new applications and modify the structure of existing projects and solutions for easy conversion, so when the time comes it will be easy to convert them to the new version of Microsoft Visual Studio.
For console applications and Windows services we will create the following folder structure.
If you need to add a middle tier project to the application to handle the business rules follow the structure below:
For web applications and web services we will leave the project file in the web application folder, so the folder structure will look like this:
If you need to add a middle tier project to the web application for the business rules:
In the first example we will prepare the My Console App console application for the conversion.
The files of the My Console App solution are distributed the following way:
The “Source” folder will contain all the source files.
Create the folder structure in Windows Explorer and in Microsoft Visual Studio 2012 move all source files to the “Source” folder, so multiple projects can reference them:
For Web Applications and Web Services leave the project file in the web application folder, and indicate the Visual Studio version in the file name:
Create a Visual Studio version specific folder for the solution and place the .sln file into it. Indicate the Visual Studio version in the name of the folder.
For console applications and windows services:
For web applications and web services:
Sometimes it makes sense the create multiple setup projects in a Microsoft Visual Studio solution if you use the same projects, but you want to create separate MSI files for slightly different functionality. An example would be the processing of audio and graphics files. You can use the same middle tier and backend projects for both processes, but deploy two versions of the application to be able to set up two separate scheduled tasks. This way you can stop them separately and set up different schedules for them.
The two setup projects can coexist, but by default they place the output MSI files to the same sub folder of the setup project: “Release” or “Debug” depending on the configuration. When you start the build of the setup project the compiler deletes all files from the target folder, so if you are expecting two MSI files after the two builds you will be surprised. You will only find the latest build result. The easiest way to handle this is to add an extra folder level in the output file name field of the setup project properties for the Debug and Release configuration.
Send the audio processing MSI to Audio\Debug and Audio\Release, and the graphics processing MSI to Graphics\Debug and Graphics\Release.
When you convert a solution to a new version of the Microsoft Visual Studio IDE you can see yellow exclamation points next to some project references. When you build the solution you also get errors like the following:
Error, The type or namespace name '...' could not be found (are you missing a using directive or an assembly reference?)
Error, Metadata file '....dll' could not be found
The yellow sign tells you that the referenced project is not compatible with this project.
Even if you remove the reference and add it again the exclamation mark stays there.
When you convert a solution to a newer version of the IDE in Microsoft Visual Studio make sure all projects target the same framework.
When Visual Studio converts a project it does not change the target framework. If you have multiple projects in your solution check the target framework on the Property pages of all of your projects to make sure those are the same.
Just for the archive
Have you ever wanted to display specific images on certain dates in the header of your WordPress page like Google does?
If you want to automatically set the header image based on the date there is an easy way to do it. This way you can display a prepared image on certain dates like Independence Day, your birthday, or as in this example on the International Women’s Day, March 8th.
In the original Witcher World WordPress theme there are two ways to display header images: one selected image or a random image from multiple uploaded header images.
If you have access to your site via FTP and are not afraid of changing some PHP script in your Witcher World WordPress theme follow the simple steps below:
<div id=”header”<?php if(get_header_image() != “”) echo ” style=’background-image: url(“.get_header_image().”);'”; ?>>
<div id=”header”
<?php
$today = date(“m-d”);
$templatedir = get_template_directory_uri();
$background_image_url = “”;
if ( “03-08″ == $today ) {
// Women’s day
$background_image_url = $templatedir.”/images/header_womens_day.jpg”;
} elseif (get_header_image() != “”) {
$background_image_url = get_header_image();
}
echo ” style=’background-image: url(“.$background_image_url.”);'”;
?>
>
On every March 8th the “header_womens_day.jpg” image will be your header image. The date(“m-d”) function returns the month and day in the UTC time zone, so you will only see the change when it is March 8th in London (8 hours ahead of Los Angeles).
If you want to print a web page on your printer without header images and advertisement
You can even delete sections of the document:
Click the buttons on the top menu to
You can remove the images by clicking the “Remove Images” box and adjust the size of the text with the “Text Size” drop down list.