Visual Studio 2010 beta 2

Oct 31, 2009 at 8:24 PM

Dear Developers. 

I was unable to install the designer on Visual Studio 2010 beta 2. I copied .cs files to project and it works... But it is impossible to develop sections. Is there any plans to move instalation of the designer for VS 2010?

Is it possible to set maually?

Nov 16, 2009 at 3:14 PM

I would also be very interested in a 2010 build as this tool in invaluable! It's the last stumbling block before I move some of my own projects to 2010 :-)

Dec 7, 2009 at 6:19 AM

So would I

--Avi

 

Coordinator
Dec 10, 2009 at 7:51 AM

I will look into this as soon as I'm moving to VS2010 myself. Until then, the tool will be targeted towards VS2008, unless somebody feels like contributing a VS2010 compatibility patch or something like that.

 

Dec 11, 2009 at 1:47 AM

What will it take to contribute to the compatibility patch?

--Avi

 

Coordinator
Dec 11, 2009 at 9:07 AM

I'm not even sure it's technically possible to create a tool in 2008 that also works in 2010. I think, when the time comes that I move to 2010, two separate versions of the tool will have to be maintained. Not exactly looking forward to that, though...

In the meantime, if using or upgrading to 2010 is very important to you, I suggest creating the configuration section designer as a separate project in 2008, compile it into a class library, and use said library from your 2010 solution.

Coordinator
Dec 11, 2009 at 11:39 AM

I suspect part of the reason the tool does not work in VS2010 is that it only registers for VS2008. It may be possible to coax it to work in VS2010 simply by changing the registry entries. If you want to try, download the source code, and in the DslSetup project, there's a file Registry.wsx. Change everything that says "SOFTWARE\Microsoft\VisualStudio\9.0" to "SOFTWARE\Microsoft\VisualStudio\10.0" and build the setup. Just beware that I haven't tested this, and that I don't recommend trying it on production code.

 

Feb 15, 2010 at 1:56 PM
alexschrod wrote:

I suspect part of the reason the tool does not work in VS2010 is that it only registers for VS2008. It may be possible to coax it to work in VS2010 simply by changing the registry entries. If you want to try, download the source code, and in the DslSetup project, there's a file Registry.wsx. Change everything that says "SOFTWARE\Microsoft\VisualStudio\9.0" to "SOFTWARE\Microsoft\VisualStudio\10.0" and build the setup. Just beware that I haven't tested this, and that I don't recommend trying it on production code.

 

Has anyone tried doing this, and are we any closer to getting a VS2010 version? With RC1 being out it'd be handy if there was an upgrade path for existing VS2008 projects.

Thanks,

Totalester.

Apr 20, 2010 at 12:39 PM

Hi,

has anyone got this great tool working with VS2010 RTM yet?

Thanks,

/Howard

Apr 22, 2010 at 9:34 AM
Hi, I started looking into this last night - but it got quite nasty, quite quickly. But I thought I'd document where I got to in case anyone decided to try it... If you have 2010 - you'll need to install Visual Studio 2010 SDK - http://bit.ly/czkKHa & Visualization & Modeling SDK: http://bit.ly/91XbVf - this is the new home of the DSL SDK. Once installed - there is actually a DSL Migration Tool that will update your previous code - simply run the tool located here: C:\Program Files\Microsoft Visual Studio 2010 SDK\VisualStudioIntegration\Tools\DSLTools\DslProjectsMigrationTool.exe Browse to the CSD solution root then click "convert" - this will update all the t4 templates. Next you'll have to search for any T4 templates that set the language to .NET 3.5 - you can delete this and the templates start to gen properly. Next you need to update the t4 references to the new VS2010 built in types (I think it's Microsoft.VisualStudio.TextTemplating.Interfaces.10.0) - at this point you will need to update the references to the types - at and this point I have up because some pretty gnarly coding updates were required and it was getting late. Hope this helps whoever tries to update this. Howard
Apr 22, 2010 at 11:44 AM
Howard,
Many thanks, I will take a look later on tonight.
Cheers,
Avi

From: [email removed]
Sent: Thursday, April 22, 2010 4:34 AM
To: [email removed]
Subject: Re: Visual Studio 2010 beta 2 [csd:73703]

From: HowardvanRooijen

Hi, I started looking into this last night - but it got quite nasty, quite quickly. But I thought I'd document where I got to in case anyone decided to try it... If you have 2010 - you'll need to install Visual Studio 2010 SDK - http://bit.ly/czkKHa & Visualization & Modeling SDK: http://bit.ly/91XbVf - this is the new home of the DSL SDK. Once installed - there is actually a DSL Migration Tool that will update your previous code - simply run the tool located here: C:\Program Files\Microsoft Visual Studio 2010 SDK\VisualStudioIntegration\Tools\DSLTools\DslProjectsMigrationTool.exe Browse to the CSD solution root then click "convert" - this will update all the t4 templates. Next you'll have to search for any T4 templates that set the language to .NET 3.5 - you can delete this and the templates start to gen properly. Next you need to update the t4 references to the new VS2010 built in types (I think it's Microsoft.VisualStudio.TextTemplating.Interfaces.10.0) - at this point you will need to update the references to the types - at and this point I have up because some pretty gnarly coding updates were required and it was getting late. Hope this helps whoever tries to update this. Howard
May 17, 2010 at 3:53 PM

Has anyone been able to figure out a way to use the designer in VS 2010?  Any help will be much appreciated.

Coordinator
May 23, 2010 at 2:01 AM

I submited a patch for 2010 support

Coordinator
May 25, 2010 at 3:38 PM

I will take another look at it, I used the debuging project to verify it would still generate code. I am sure I missed something.

 

Coordinator
May 25, 2010 at 7:47 PM

Uploaded another patch see comments in vs 2010 issue.

Coordinator
May 26, 2010 at 6:31 PM

Ah.....

I did  not remove dslsetup from my zip I should have. Remove dsl setup, and any other references to csd. Then run DslPackage\bin\Debug\ConfigurationSectionDesigner.DslPackage the "setup" projects are not used in 2010 any more. I don't know what the ramification would be to somone who needs both the 2008 and 2010 versions installed. I only run 2010.

Coordinator
May 26, 2010 at 9:28 PM

Interesting...I will try to get this installed on a system that has never seen it before.

 

 

 

Do you also have vs 2008 with the old csd installed?

Coordinator
Jun 3, 2010 at 5:15 AM

I can reproduce the problem, looking into the solution will be a few days.

Coordinator
Jun 3, 2010 at 8:37 PM

Hi all,

I'm the original author of this project so I'm sorry it took me so long to jump in but I really haven't had the time to look into this yet. Anyway, since TheMrKeys has been busy working on VS2010 support (which I agree would be awesome) I've made him coordinator on this project too so he should be able to check his changes in directly and publish new versions of this project and such. Hopefully by eliminating myself as a bottleneck his great work will be able to make it into the project much quicker.

Thanks in advance!

-Jelle

Coordinator
Jun 3, 2010 at 8:39 PM

The tool is great I have come to use it a lot. The core of the code is a great concept I had never thought of. Would you like to create a separate branch for the 2010 code?

From: jelled [mailto:notifications@codeplex.com]
Sent: Thursday, June 03, 2010 3:38 PM
To: Ryan Faircloth
Subject: Re: Visual Studio 2010 beta 2 [csd:73703]

From: jelled

Hi all,

I'm the original author of this project so I'm sorry it took me so long to jump in but I really haven't had the time to look into this yet. Anyway, since TheMrKeys has been busy working on VS2010 support (which I agree would be awesome) I've made him coordinator on this project too so he should be able to check his changes in directly and publish new versions of this project and such. Hopefully by eliminating myself as a bottleneck his great work will be able to make it into the project much quicker.

Thanks in advance!

-Jelle

Read the full discussion online.

To add a post to this discussion, reply to this email (csd@discussions.codeplex.com)

To start a new discussion for this project, email csd@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

Coordinator
Jun 5, 2010 at 2:58 PM

The VS 2010 beta release has been posted, please give it a shot, log issues in issue tracker.

 

Coordinator
Jun 7, 2010 at 2:21 PM
It's marked beta first not release. The code gen worked for me but so did some other things you reported before. I'm sure it's a deployment issue.

1.x will be maintained for vs 08
2. Will be vs 2010

The project template was just the library with the csd item added. For beta I didn't bother with it.



-- Sent from my Palm Pre


On Jun 7, 2010 9:16 AM, TheRHCP <notifications@codeplex.com> wrote:

From: TheRHCP

I finally tried it.

What is surprising is that code generation does not work anymore. I first tried on an existing project without results and then I created a new project, added some sections no CS file has been generated.

I also noticed that when I tried to add something in a Section (right click), an error message is poping up ("Value does not fall within the expected value").

Then I also noticed that the project template disappeared, only the item template stayed.

I know that this is a beta version, but I do not think that this is right to make a realease for it as it is almost unusable.

Same thing concerning the version number, no major changes so why a major version ?

Coordinator
Jun 7, 2010 at 2:58 PM

I can recreate this on my second machine but not the machine I did the development on so this is a deployment issue. I’m learning the VS experimental shell for debugging is not as isolated as I thought.

I will try to work on this tonight I can’t this morning.

From: TheRHCP [mailto:notifications@codeplex.com]
Sent: Monday, June 07, 2010 9:16 AM
To: Ryan Faircloth
Subject: Re: Visual Studio 2010 beta 2 [csd:73703]

From: TheRHCP

I finally tried it.

What is surprising is that code generation does not work anymore. I first tried on an existing project without results and then I created a new project, added some sections no CS file has been generated.

I also noticed that when I tried to add something in a Section (right click), an error message is poping up ("Value does not fall within the expected value").

Then I also noticed that the project template disappeared, only the item template stayed.

I know that this is a beta version, but I do not think that this is right to make a realease for it as it is almost unusable.

Same thing concerning the version number, no major changes so why a major version ?

Read the full discussion online.

To add a post to this discussion, reply to this email (csd@discussions.codeplex.com)

To start a new discussion for this project, email csd@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

Coordinator
Jun 7, 2010 at 4:12 PM

I too find the decision to make the VS2010 version 2.0 a bit weird. It's not like you'd make an application that was made with .NET 1.1 be v1.x and as soon as you switched to .NET 2.0 make your application v2.x. I find it particularly bothersome, because I was considering making a 2.0 release of the VS2008 tool sometime, which now won't be possible, or at the very least get rather confusing.

Coordinator
Jun 7, 2010 at 4:21 PM

Since naming the VS2010 edition v2.0 was my idea I guess I should chime in :-)

I agree that there aren't a lot of new features to warrant a major version number update, but I would also find it very confusing to have a v1.6.1 that works with VS2008 and a v1.7 for example that works with VS2010. And then a v2.0 for VS2008 and a v2.1 for VS2010? I don't know... So maybe it would be better to keep the real version number the same then (as long as the functionality is the same) and just name the releases on CodePlex differently, e.g. "v1.7 for VS2008" and "v1.7 for VS2010"? But then these should be functionally equivalent or it will be even more confusing. So Alex, if you'd add a bunch of features for v2.0 then I hope a VS2010 edition with the same features would be on the roadmap?

In the end, you guys do what you think is best, at this point I'm just not involved enough to push any opinion either way.

Cheers,

Jelle

Coordinator
Jun 7, 2010 at 4:37 PM

Since I have not yet used VS2010, I cannot really give good input here, but if (and only if) most of the code is the same still, it should be possible to merge changes made in either branch back and forth as they are being made. That way, the two branches would stay in sync. Alternatively, it could be made a policy that any feature added in one branch also has to be added in the other. The final option is to let the two branches divert and become separate tools, meaning that you can't expect things to work the same in the VS2008 version and the VS2010 version. I've put my alternatives in the order that I prefer things take place... i.e. kept-in-sync-by-merge branches are best, kept-in-sync-but-not-by-merge branches are the second best, and diverting tools the least good option.

That's my opinion, anyway. I've already given my opinion on the versioning issue, meaning I don't think a VS2010 release automatically makes the tool v2.0. Honestly, I think more discussion should be done on the whole versioning issue before a final decision is made.

Coordinator
Jun 7, 2010 at 5:43 PM

The conversion process from the old SDK to the new DSL sdk makes breaking changes from the looks of it. The "generated code" tt files are very different from the old once. While someone may know of a way to include both the old and new files and conditionally generate code I don't. While I am interested in working out the 2010 version. I don't think I would have the time or interest to back port changes to the 2008 version. The deployment also changes a lot. the VSIX does all the lifting now in ways the 08 VSIX could not. We don't use the setup at all any more in 2010.

 

Jelle suggested the branch I agreed with him, I am open to suggestions, we could do something like 2010 v1.7 and 2008 v1.7 but the differences in deployment could be very confusing over time. I think any way we go confusion will occur.

Jun 24, 2010 at 8:04 AM

Hello guys

anyone can point me where can I download v2.0 for VS 2010? :(

thanks

Jun 24, 2010 at 2:49 PM

Error 1 The type or namespace name 'CoreCopyClosure' does not exist in the namespace 'Microsoft.VisualStudio.Modeling' (are you missing an assembly reference?) C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\DomainModel.cs 523 44 Dsl
Error 2 The type or namespace name 'CoreDeleteClosure' does not exist in the namespace 'Microsoft.VisualStudio.Modeling' (are you missing an assembly reference?) C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\DomainModel.cs 543 46 Dsl
Error 3 Could not load file or assembly 'VSCTCompress.dll' or one of its dependencies. The specified module could not be found. DslPackage
Error 4 'Microsoft.VisualStudio.Modeling.SerializationUtilities' does not contain a definition for 'WriteExtensions' C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\SerializationHelper.cs 149 40 Dsl
Error 5 'Microsoft.VisualStudio.Modeling.SerializationUtilities' does not contain a definition for 'ExtensionsXmlElementName' C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\SerializationHelper.cs 175 84 Dsl
Error 6 'Microsoft.VisualStudio.Modeling.SerializationUtilities' does not contain a definition for 'ReadExtensions' C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\SerializationHelper.cs 177 41 Dsl
Error 7 'Microsoft.VisualStudio.Modeling.SerializationResult' does not contain a definition for 'Encoding' and no extension method 'Encoding' accepting a first argument of type 'Microsoft.VisualStudio.Modeling.SerializationResult' could be found (are you missing a using directive or an assembly reference?) C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\SerializationHelper.cs 430 31 Dsl
Error 8 'Microsoft.VisualStudio.Modeling.SerializationResult' does not contain a definition for 'Encoding' and no extension method 'Encoding' accepting a first argument of type 'Microsoft.VisualStudio.Modeling.SerializationResult' could be found (are you missing a using directive or an assembly reference?) C:\Users\Davita\Desktop\Main-VS2010\Source\Dsl\GeneratedCode\SerializationHelper.cs 586 24 Dsl

I'm unable to compile with VS SDK Beta 1 and DSL Sdk Beta 1. Of course I'm using VS 2010 :D (stable)

any help? :(

Jun 25, 2010 at 1:02 AM
Edited Jun 25, 2010 at 1:02 AM

I would agree with TheRHCP, I would leave this version as a VS2008 version 1.7 being the final major release for VS2008 then start a new project for Configuration Section Designer 2010 which is VS2010 support for the new DSL SDK which might hopefully also work on the next iteration of VS.

Personally it will just be confusing otherwise as they don't really branch from a common base due to the differences between VS2008 and VS2010.

 

Just my two cents

Aug 3, 2010 at 6:12 PM
I agree with aussiealf. I don't think having a "Configuration Section Designer 2010" is confusing at all ... either that or just break off on another name altogether.
Aug 8, 2010 at 3:46 PM
Edited Aug 8, 2010 at 3:47 PM

Do not put so much thought in what number is has to have, it does not matter for the users anyways. They will click on the button that has the right visual studio version :)

You need to consider that in a couple of years, another VS version will come out. How long do you expect to work on/support the VS2008 version. Do you plan on extending the functionality, or do you want to make it rock stable?

Imho, make a VS2008 branch and put it in maintenance-mode. Only fix bugs and issues. Make that 1.X. Make VS2010 2.0.

Great work by the way, i love it.

Sep 2, 2010 at 11:59 AM

That would be my suggestion, too.

Also I just wanted to let you know: We are currently using Configuration Section Designer from the latest SVN revision (48968) under VS2010 in a productive environment! Although there are some minor issues that can be worked around (like clicking right mouse button), it's working great. We built up all the configuration sections over different namespaces from scratch, and added validator-methods in partial class files.

We even made the .xsd Style Sheet be referenced in App.config, with code hint and syntax check working! For this it is necessary to add xmlns="your_xml_namespace" attribute to the configuration sections in App.config. After that, the generated code fails to work, because "xmlns" is not known configuration attribute obviously. Don't try to add a dummy "xmlns" attribute to every configuration section in the modeller! Even though this will make your project compile again, it will break code-hint and syntax check in App.config. Instead add a partial class with the same name and add an xmlns property to it manually. You could first create it in the modeller and then move the code for it over to your own class. This way you can design and generate freely in the modeller, even in multiple csd files, and the App.config syntax is checked instantly against the newly generated xsd files.

Long story short: I can recommend using latest CSD in VS2010 and hope there is a stable release soon.

Sep 12, 2010 at 6:22 PM

@BobBaum:

I'm not seeing the success that you are.  I've downloaded the revision, compiled the .vsix, and then created a new project and added a .csd to it.  I add a configuration section and try to build and I get errors in the generated code about identifiers being expected.  It seems to want to try and create a type name from a namespace, which seems completely wrong to me.

Could you give more detail on either what you did to get to this "working" state or on what gotchas/issues there are?

Also, without being able to right click, how can one add attributes to their elements without having to code them in the csd file by hand?  That seems like a pretty big issue.

Thanks for all the great work.

- Nick

Oct 14, 2010 at 10:49 AM

I miss the old times where nobody had a mouse and everybody knew intuitively that inserting an attribute would work by pressing INSERT on the keyboard. ;-)

Simply adding a configuration section doesn't make a valid configuration. You have to at least ...

- add the section (mouse drag'n'drop from tool bar)
- click at a blank spot outside the section and define the "Xml schema namespace" and the "Namespace" in the Properties for the Configuration Section Model
- Save the model (by that the custom tool will generate your files)

At least that's how it worked for us. Of course not with the first try, but after some testing with blank projects we worked it out...

Bob

Oct 19, 2010 at 10:00 AM

No news for VS 2010 build?

Coordinator
Oct 19, 2010 at 12:17 PM

No I haven’t been able to work on it L

From: Dato0011 [mailto:notifications@codeplex.com]
Sent: Tuesday, October 19, 2010 5:00 AM
To: Ryan Faircloth
Subject: Re: Visual Studio 2010 beta 2 [csd:73703]

From: Dato0011

No news for VS 2010 build?

Read the full discussion online.

To add a post to this discussion, reply to this email (csd@discussions.codeplex.com)

To start a new discussion for this project, email csd@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

Nov 16, 2010 at 9:10 PM

Hello,

I recently migrated my solution to 2010. I was successfully compiled and installed version 2.0 for VS2010. I am encountering the known issues:

 

-Unable to Create a new csd project in vs2010

-Designer shows an error with right clicking in the Designer.

 

I am big fan of this project and has help me tremendously. Do you know if there is a work around or a update planned?

 

I am using vs2010 ultimate on windows 7 x64. I also have vs2008 installed on my machine

Nov 19, 2010 at 9:38 PM

I love this concept but need it for 2010, I've tried to install it but it have the same right click issues.

 

Do you have an ETA for the next release?

Nov 21, 2010 at 6:45 PM

In the absence of a solid version that works with VS 2010, the source code would be nice.  {-o)

Nov 22, 2010 at 1:46 PM
Edited Nov 22, 2010 at 1:51 PM

Hello,

I am also using the VS2010 version and I also encounter the right-click problem in the Designer. Been having this problem for every VM that I test it on. I was about to give up using the tool because of the error, so I decided to try it for the last time on another VM. This time the CSD tool worked perfectly and I can see/use the context menu after a right click. I don't know why it worked in this other VM because all of the VMs I tested it on came from the same image.

Does anyone have any idea on what's causing this error? Do you have any suggestions on how to fix this?

 These are the errors I am getting:

  • Value does not fall within the expected range
  • The parameter is incorrect (Exception from HRESULT: 0x80070057 (E_INVALIDARG))

Thanks.

 

Nov 22, 2010 at 6:17 PM

hi Idiz,

 

You were able to get it to work in one vm?   What version did you compile. I tried using 2.0.0 and Main-vs2010 had no luck =(

Nov 22, 2010 at 7:13 PM

The known issue with the right click can be found here. Please continue to vote this issue

 

http://csd.codeplex.com/workitem/6922

 

Jan 17, 2011 at 2:10 AM

Hi,

 

Was wondering if there has been any plans for updates to the VS2010 version.  I tried the Main-VS2010 version on two different systems and get the same right click error previously mentioned.  I'd like to be able to use this tool myself.

 

Thanks,

 

WedgeBones

Jan 17, 2011 at 4:47 AM

Today I was able to generate a version from VS2010 using BobBaum advice (once I read the full text of the post).

  1. Create a new project (I used VB as that is what I need at work ATM)
  2. Add new item, choose "Configuration Section Designer"
  3. Open the *.csd file
  4. Drag Configuration Section to canvas
  5. Left Click in the white area of the canvas
  6. Add Assembly Name, Namespace and Xml Schema Namespace properties
  7. Drag Configuration Element to canvas
    1. give it a name
  8. LEFT click the Elements item of the configuration Section
  9. press INSERT on keyboard (thanks @BobBaum) enter a valid name
  10. LEFT click the new item and move to the Properties window to select the Type)

the same thing will work for adding a Collection

to add an attribute

  1. LEFT click the Attributes section of the configuration item to add attributes to
  2. press INSERT on keyboard and enter a valid name
  3. choose Type in properties window
  4. save