VS and SQL 2005
Adventures in the world of VS 2005 and SQL 2005
Came across a very interesting video on Channel 9 dealing with the future BizTalk Solution Designer. It looks really good and now i cant wait to get my hands on it. I was thinking of experimenting with DSL's in VS2005 and building something that does a very similar task, to be able to graphically sketch out stuff from receieve adapters, through locations, pipelines, orchestrations and into the message box (and out again). And I want to be able to use GAT packages , project templates and so on. Well, we might have some of that when the official tool comes out.
The only 'drawback' perhaps, is that it isnt built using the Whitehorse kind of design surface nor is it done with the DSL design tools available today. Now this could be for a very good reason. The AD surface probably just isnt rich enough (and when you see the whizzy stuff in the BTS SD like the redrawing and consolidation of shapes you will understand why) and the DSL tools are still in a very early stage, although some folks are managing to put them to good use (such as the DSL that goes with WSCF) But Im sure this wont be insurmountable. After all, they are looking at a release date beyond 2006 for this tool and the DSL team would sure love to get their hands on a real world killer application (not to mention that AD could be done with the DSL designer too, the ultimate dog-fooding) which would help them mature their product really quickly.
The other reason they should do it is for platform/tool coherence sake. As it is there is a big divergence in tools. I discussed this with some of the project team reps in TechEd Amsterdam. For instance Beat Schwegler demo'ed the Melted Cheese GAT package where his webservice consisted of around 8 projects. That was all well and good, but if you put a Webservice in your project design surface in AD, it generates a single project. There is no way to customize it to make it generate an entire solution for the WS like the GAT package would have us do, neither can it use Enterprise Templates, nor can it even be customized with Project Templates (the simplest of the lot) so that doesnt leave architects with many options if you want to spec out a multi solution architecture (of course you could manually refactor the stuff and extract the WS into its own solution and have an AD for that alone) but then you lose some of the point of using the AD in the first place as it would be just a pretty model. Apparently there are some efforts on to get some convergence in these tools so that architecture creation and representation is more consistent and I for one am very eager to see the progress here.
So coming back to the point, I like the idea of the solution designer and for MS sake i hope things progress to the point where this utilises the DSL designer. Wonder what Steve Cook would say to this.
I got a flood of nearly 50 spam messages in a single day (a couple of days ago) and Donny Mack has said that they definitely are doing something ASAP. So i'm waiting.
Anyway, on the lines of my previous post on Whitehorse extensibility, here's my postulation on extending the class designer. My idea is to use the class designer and with OR mapping principles, make it generate a database design.
The generation will have to highly customizable because DDL generation is a highly sensitive thing for database folk and from personal experience i know that some OR mappers (that take class design as input) generate some primitive DDL thats quite useless.
It should be interesting to take this further into XML message design and so on.
I just found a really cool blog with posts from the Whitehorse team. There are articles on how to generate the Deployment Report, manage the dozens of constraints and settings in the Application Designer and so on.
I think there is great potential in the Whitehorse toolset. Here are my thoughts/visions on the extensibility. Some of these might be basic (and folk might be doing it already) and some might be impossible, but hey, lets see.
(1) Extend it so that it generates projects using custom enterprise templates.
(2) Add in symbols for Ent Lib so we can add in the required blocks automatically
(3) A 'deployment package' view where you can state which package hold which assembly and where it goes. For instance, in my previous project we had a mix of console apps, DLL's and web apps. When we deployed them we combined some console apps into one project and used command line switches to execute the required pieces. We could potentially do this diagrammatically.
(4)Taking this one step further, you could probably link into App Centre when deploying to farms. I would also like it to trigger the entire build and deploy process. Jeff mentioned (in the above said blog) how some people were just happy with the XML deployment report and wanted to script their own deployments cos they didnt want MS putting stuff on their boxes!! Thats fine for some. I'd be happy to have an automated deployment option.
There's some of my ideas. Does it resound with anyone? think its rubbish?