Michael Freidgeim's Blog

I have a big solution in VS 2005 that I converted to VS 2008. However each time when I closing and then re-opening solution, the Conversion Wizard opens again, runs for some time and shows that conversion completed successfully.

UPDATE: I finally found the reason of re-running of Conversion Wizard. My solution had some UNLOADED projects, that were in VS 2005 format and failed to be converted.  I expected that unloaded projetcs will be ignored , but Conversion Wizard each time tried to convert them. After I removed UNLOADED not-converted projects from the solution, Conversion Wizard is not ivoked any more.

It regenerates some DataSet.Designer.cs,  in generated file shows "Runtime Version:2.0.50727.1433"(which is good-compatible with 2005).
Conversion report doesn't show designer.cs files as converted, and the parent project has status-no conversion required.

I couldn't find any problems in the solution file.

 The solution has first line: 

Microsoft Visual Studio Solution File, Format Version 10.00

which should be sufficient according to How to use solutions and projects between Visual Studio 2005 and 2008

 The similar issue discussed in thread Confusion when opening VS 2005 project in VS 2008

 Related links (that do not help with my problem):
Don't sweat migrating legacy .NET projects to Visual Studio 2008

 I hate and loath the Visual Studio Conversion Wizard

 The ProjectConverter application to convert back and forth between VS2005 and VS2008 is available at: http://home.hot.rr.com/graye/Articles/ProjectConverter.htm
It will be good if the converter be able to open individual project files, not solutions only.

 Rick Strahl's Moving Projects/Solutions between Orcas and Visual Studio 2005 

 and my own post Problems after Installing VS 2008 side-by-side with VS 2005

In MOM 2000 there is no ability to quickly find which rules use the script.

I found a script in MOM/Rules/Advanced/Scripts/  ( or alternatively in DB one point Script table) and my question was which rules run the script.

Use [OnePoint].[dbo].[ProcessRuleToScript] table to find the rules.

select * from [OnePoint].[dbo].[ProcessRuleToScript]

where Idscript='5c4a58cf-709c-4a1f-895a-0aec79ff55a9'(this GUID is just example)

select * from [OnePoint].[dbo].[ProcessRule]

where idProcessRule in

(

select idProcessRule from [OnePoint].[dbo].[ProcessRuleToScript]

where Idscript='5c4a58cf-709c-4a1f-895a-0aec79ff55a9'

)