Project Upgrader Tutorials
Check out these tutorials and learn how to use the WEBfactory2010 Project Upgrader tool by following the described steps.
Upgrading Expression Blend/Visual Studio projects to a newer WEBfactory 2010 version, using WEBfactory 2010Project Upgrader
Check out this article and learn how to upgrade Epression Blend and Visual Studio porjects to a newer version, using Project Upgrader.
IMPORTANT:
Add the following DLL files from the Silverlight4/Standard folder to the project's folder, and reference them in the project:
Microsoft.Expression.Controls.dll
System.Reactive.dll
The following DLL files must be remove from the project's references:
Telerik.Windows.Controls.RadRichTextBoxRibbonBarUI.dll
Telerik.Windows.Controls.RibbonBar.dll
The upgrade process is made automatically using WEBfactory 2010Project Upgrader Wizard, by changing the references to the actual versions.
WEBfactory 2010 Project Updater
To update a project to the desired version, follow the steps indicated by the WEBfactory 2010Project Upgrader Wizard:
Select the solution you want to upgrade. The original solution will not be changed, the upgrade being made after the solution is copied to the target location.
Select the target folder where the upgraded project will be copied - the folder must not exist on your machine, the WEBfactory 2010Project Upgrader will automatically create the folder. This is a security measure used to avoid overwriting existing files.
To select the target folder, browse to the folder where you want the target folder to be created, select Ok and type the folder you want to create as target folder (see image above).
The Full path of the upgraded solution box will display the full path of the solution.
Select the folder that contains the Silverlight controls to which you want to upgrade - the new version of Silverlight controls
If the folder that contains the Silverlight controls is located inside the project folder, the WEBfactory 2010Project Upgrader will set relative paths in the upgraded project, pointing to the Silverlight controls folder. This allows the user to move the project on another computer, without depending on a fixed path for the Silverlight controls folder.
If the folder that contains the Silverlight controls is located somewhere outside the project folder, the WEBfactory 2010Project Upgrader will set an absolute path pointing to he Silverlight controls folder. This makes the upgraded project to depend on the Silverlight controls folder location.
Click Next to continue. The next window will display a list of projects from the selected solution that will be upgraded.
Click Finish to start the process.
After the process is complete, the results are displayed:
The projects with the status Success have been upgraded.
The projects with the status Skipped are the web projects that don't have any reference to upgrade. This is not an error.
The complete solution with the upgraded references can be found in the target folder. The original solution is not affected by the upgrade process.
Upgrading Expression Blend/Visual Studio containing re-skinned controls to a newer WEBfactory 2010 version
Check out this article and learn how to upgrade Expression Blend and Visual Studio containing re-skinned controls to a newer version.
For this tutorial, the WEBfactory 2010 Demo Project will be used as example project.
In order to upgrade the solutions to a newer version of WEBfactory 2010 , the following steps need to be performed:
The following steps are available only for projects with re-skinned WEBfactory 2010 controls. Projects containing stock WEBfactory 2010 controls are upgraded using the WEBfactory 2010Project Upgrader only. The next steps are not necessary because the DialogControl, MessageBoxControl and WFWriteSecureDialog are not written in the XAML code.
For projects containing custom made controls, a different workflow is required:
Click here to read more about upgrading projects containing custom controls or user controls.
Upgrade the project using the WEBfactory 2010Project Upgrader.
Clean and build the solution.
Remove DialogControl, MessageBoxControl and WFWriteSecureDialog from the projects XAML. The Dialogs cannot be written in XAML code for the 3.3 version of WEBfactory 2010 .
Check the dependencies after the above steps are complete. This is needed because some of the dependencies might be third party; the build might show no errors, but the control might not work properly at design time or run time.
Upgrade the project using the WEBfactory 2010Project Upgrader
Follow the Upgrading Expression Blend/Visual Studio projects to a newer WEBfactory 2010 version, using WEBfactory 2010Project Upgrader guide to upgrade the project to the latest WEBfactory 2010 version.
Proceed with the next steps after the upgrade is complete.
Clean and build the solution
Using Expression Blend
Open the upgraded project in Expression Blend. Right-click on the solution in the Projects panel and select Clean Project.
Right-click again on the solution and select Build Project. Alternatively, you can press F5 to start building the solution.
After the build succeeded, proceed to the next step.
If the solution you are upgrading contains incompatible code, the build will not succeed.
Using Visual Studio
Open the upgraded project in Visual Studio. Right-click on the solution in the Solution Explorer and select Clean Solution.
Right-click again on the solution and select Build Solution. Alternatively, you can press F6 to start building the solution.
After the build succeeded, proceed to the next step.
If the solution you are upgrading contains incompatible code, the build will not succeed.
Remove DialogControl, MessageBoxControl and WFWriteSecureDialog from the projects XAML
Using Expression Blend
In order to successfully upgrade the project to the latest WEBfactory 2010 version, it is necessary to remove DialogControl, MessageBoxControl and WFWriteSecureDialog tags from each XAML file of the solution. For this, we will use the Find tool from Expression Blend (Edit > Find or Ctrl + F).
Using the Find tool to locate and delete the necessary tags
Using the Find in Files utility, all the XAML files form the project can be searched simultaneously. Use the Find in Files option and select XAML for the File Types. Apply the Find in Files on the entire solution.
The Find in Files results panel will list the found lines in all the XAML files. Double-clicking a result line in the results panel will open the XAML document containing the line and will set the cursor on that specific line.
In order to correctly remove the desire tags, make sure that the entire tag is deleted. In some situations, the tag may spread across multiple lines of code.
Repeat the procedure for all of the DialogControl, MessageBoxControl and WFWriteSecureDialog tags from all the XAML files from the solution.
Using Visual Studio
In order to successfully upgrade the project to the latest WEBfactory 2010 version, it is necessary to remove DialogControl, MessageBoxControl and WFWriteSecureDialog from each XAML file of the solution. For this, we will use the Find and Replace tool from Visual Studio.
Using the Find and Replace tool to locate and delete the necessary tags
Using the Find and Replace utility, all the XAML files form the project can be searched simultaneously. The easiest way is to use the Find in Files option and select the File Types that include XAML.
The Find Results panel will list the found lines in all the XAML files. Double-clicking a result line in the Find Results panel will open the XAML document containing the line and will set the cursor on that specific line.
In order to correctly remove the desire tags, make sure that the entire tag is deleted. In some situations, the tag may spread across multiple lines of code.
Repeat the procedure for all of the DialogControl, MessageBoxControl and WFWriteSecureDialog tags from all the XAML files from the solution.
Check the dependencies after the above steps are complete
This is needed because some of the dependencies might be third party; the build might show no errors, but the control might not work properly at design time or run time.
Please refer to the Controls and References documentation for checking the dependencies. Make sure that all the required dependencies are referenced in the project.
After the upgrading steps are complete, the solution can be opened in Expression Blend for testing. A correct upgrade procedure will result in a working Blend project. If any errors occur, check if all the tags were removed from all the XAML files in step 3.
Updating Expression Blend/Visual Studio projects with custom controls to a newer WEBfactory 2010 version
Check out this article and learn how to update Expression Blend and Visual Studio projects with custom controls to a newer version.
When upgrading a project that contains custom controls/user controls to a new WEBfactory 2010 version, the custom controls/user controls must be edited in order to remove the DialogControl, MessageBoxControl and WFWriteSecureDialog from XAML and place it in the code source.
In order to upgrade the solutions to a new version of WEBfactory 2010 , the following steps need to be perfomed:
The following steps are available only for projects with custom controls and user controls. Projects containing stock WEBfactory 2010 controls are upgraded using the WEBfactory 2010Project Upgrader only. The next steps are not necessary because the DialogControl, MessageBoxControl and WFWriteSecureDialog are not written in the XAML code.
For projects containing re-skinned controls, a different workflow is required:
Click here to read more about upgrading projects containing re-skinned controls.
Upgrade the project using the WEBfactory 2010Project Upgrader.
Clean and build the solution.
Remove DialogControl, MessageBoxControl and WFWriteSecureDialog from the projects XAML. The Dialogs cannot be written in XAML code for the 3.3 version of WEBfactory 2010 .
Create the DialogControl, MessageBoxControl and WFWriteSecureDialog in code.
Check the dependencies after the above steps are complete. This is needed because some of the dependencies might be third party; the build might show no errors, but the control might not work properly at design time or run time.
Upgrade the project using the WEBfactory 2010Project Upgrader
Follow the Upgrading Expression Blend/Visual Studio projects to a newer WEBfactory 2010 version, using WEBfactory 2010Project Upgrader guide to upgrade the project to the latest WEBfactory 2010 version.
Proceed with the next steps after the upgrade is complete.
Clean and build the solution
Using Expression Blend
Open the upgraded project in Expression Blend. Right-click on the solution in the Projects panel and select Clean Project.
Right-click again on the solution and select Build Project. Alternatively, you can press F5 to start building the solution.
After the build succeeded, proceed to the next step.
If the solution you are upgrading contains incompatible code, the build will not succeed.
Using Visual Studio
Open the upgraded project in Visual Studio. Right-click on the solution in the Solution Explorer and select Clean Solution.
Right-click again on the solution and select Build Solution. Alternatively, you can press F6 to start building the solution.
After the build succeeded, proceed to the next step.
If the solution you are upgrading contains incompatible code, the build will not succeed.
Remove DialogControl, MessageBoxControl and WFWriteSecureDialog from the projects XAML.
The properties of the DialogControl, MessageBoxControl and WFWriteSecureDialog controls will be recreated in code source.
Using Expression Blend
In order to successfully upgrade the project to the latest WEBfactory 2010 version, it is necessary to remove DialogControl, MessageBoxControl and WFWriteSecureDialog tags from each XAML file of the solution. For this, we will use the Find tool from Expression Blend (Edit > Find or Ctrl + F).
Using the Find tool to locate and delete the necessary tags
Using the Find in Files utility, all the XAML files form the project can be searched simultaneously. Use the Find in Files option and select XAML for the File Types. Apply the Find in Files on the entire solution.
The Find in Files results panel will list the found lines in all the XAML files. Double-clicking a result line in the results panel will open the XAML document containing the line and will set the cursor on that specific line.
In order to correctly remove the desire tags, make sure that the entire tag is deleted. In some situations, the tag may spread across multiple lines of code.
Repeat the procedure for all of the DialogControl, MessageBoxControl and WFWriteSecureDialog tags from all the XAML files from the solution.
Using Visual Studio
In order to successfully upgrade the project to the latest WEBfactory 2010 version, it is necessary to remove DialogControl, MessageBoxControl and WFWriteSecureDialog from each XAML file of the solution. For this, we will use the Find and Replace tool from Visual Studio.
Using the Find and Replace tool to locate and delete the necessary tags
Using the Find and Replace utility, all the XAML files form the project can be searched simultaneously. The easiest way is to use the Find in Files option and select the File Types that include XAML.
The Find Results panel will list the found lines in all the XAML files. Double-clicking a result line in the Find Results panel will open the XAML document containing the line and will set the cursor on that specific line.
In order to correctly remove the desire tags, make sure that the entire tag is deleted. In some situations, the tag may spread across multiple lines of code.
Repeat the procedure for all of the DialogControl, MessageBoxControl and WFWriteSecureDialog tags from all the XAML files from the solution.
Create the DialogControl, MessageBoxControl and WFWriteSecureDialog in code.
When the content of the window is defined in XAML, in order to proceed with the upgrading steps, the content needs to be extracted into a custom/user control. The custom/user control must be instanced in the code and referenced in the content property of the window.
Supposing that in the project XAML we use all of our removable controls (the DialogControl, MessageBoxControl and WFWriteSecureDialog). The tags that we removed in the third step (see above) would look like this:
<WFShared:DialogControl x:Name="DC1" Content="DialogControl" Width="100" Height="100" Grid.RowSpan="2" /> //for DialogControl
<WFShared:MessageBoxControl x:Name="MB1" Content="MessageBoxControl" Width="100" Height="100" Grid.RowSpan="2" /> //for MessageBoxControl
<WFShared:WFWriteSecureDialog x:Name="WSD1" Content="WFWriteSecureDialog" Width="100" Height="100" Grid.RowSpan="2" /> //for WFWriteSecureDialog
When working with user controls, the object can be created in the constructor. When working with custom controls, the object needs to be created in the OnApplyTemplate method!
Once the DialogControl, MessageBoxControl and WFWriteSecureDialog are removed from XAML, create the three objects in the code source:
Declare the objects:
private DialogControl DC1; //for DialogControl private MessageBoxControl MB1; //for MessageBoxControl private WFWriteSecureDialog WSD1; //for WFWriteSecureDialog
Create the objects in the constructor (for User Controls) or in the OnApplyTemplate method (for Custom Controls):
CreateDialogControl(); //for DialogControl
CreateMessageBoxControl (); //for MessageBoxControl
CreateWFWriteSecureDialog (); //for WFWriteSecureDialog
Create the corresponding methods:
private void CreateDialogControl() //for DialogControl { DC1 = new DialogControl(); DC1.Content = "DialogControl"; DC1.Width = 100; DC1.Height = 100; }private void MessageBoxControl() //for MessageBoxControl { MB1 = new DialogControl(); MB1.Content = "MessageBoxControl"; MB1.Width = 100; MB1.Height = 100; }private void WFWriteSecureDialog() //for WFWriteSecureDialog { WSD1 = new DialogControl(); WSD1.Content = "WFWriteSecureDialog"; WSD1.Width = 100; WSD1.Height = 100; }
Check the dependencies after the above steps are complete.
This is needed because some of the dependencies might be third party; the build might show no errors, but the control might not work properly at design time or run time.
Please refer to the Controls and References documentation for checking the dependencies. Make sure that all the required dependencies are referenced in the project.
After the upgrading steps are complete, the solution can be opened in Expression Blend for testing. A correct upgrade procedure will result in a working Blend project. If any errors occur, check if all the tags were removed from all the XAML files in step 3.
Upgrading Expression Blend/Visual Studio projects containing the User Manager control to a newer WEBfactory 2010 version
Check out this article and learn how to upgrade Expression Blend and Visual Studio projects containing the User Manager control.
The upgrade of an Expression Blend (or Visual Studio) project that contains the WEBfactory 2010 User Manager control must be done in two steps:
Upgrading the project using the WEBfactory 2010Project Upgrader tool;
Manually upgrading the WFUserManagementRIAServices.dll.
Upgrading the project using the WEBfactory 2010Project Upgrader
To upgrade the project that contains the WEBfactory 2010 User Manager using the WEBfactory 2010Project Upgrader tool, click on the link below and follow the guide:
Once the upgrading procedure is complete, continue to the next step.
Manually upgrading the WFUserManagementRIAServices.dll
After the project has been upgraded using the WEBfactory 2010Project Upgrader, follow one of the next steps:
In the examples below, the upgraded User Manager project is called UserManagerProject.
Only one of the tree steps is required for upgrading the WFUserManagementRIAServices.dll!
Copy the WFUserManagementRIAServices.dll from WEBfactory 2010\Studio\UserManager\bin to the UserManagerProject\UserManagerProjectSite\bin folder and overwrite the existing DLL file.
Go to Program Files (x86)\Microsoft Expression\Blend 4\ProjectTemplates\en\CSharp\Silverlight\WFWebSite and open the csWFSilverlightWebsite.zip archive (the template project for any WEBfactory 2010 projects in Expression Blend). Copy the WFUserManagementRIAServices.dll from csWFSilverlightWebsite.zip\Site\bin to the UserManagerProject\UserManagerProjectSite\bin folder and overwrite the existing DLL file.
Create a new WEBfactory 2010 project in Expression Blend (using the 3.3 version of WEBfactory 2010). Open the project's folder and copy the WFUserManagementRIAServices.dll file from the NewWFProject\NewWFProjectSite\bin to the UserManagerProject\UserManagerProjectSite\bin folder of the upgraded project and overwrite the existing DLL file.