Is this worth the pain?

Apr 8, 2008 at 8:29 PM
Edited Apr 8, 2008 at 9:15 PM
I am becoming more and more frustrated by the bugginess within the DSL.
I think I am just venting, but here are my pain points:
1. Refactoring is very difficult without some sort of drag drop between models.
2. Validation errors are very difficult to track down. I am left with deleting messages/operation/datacontracts one by one until I find the culprit entity.
3. Being forced to edit the datacontract file by hand to change Primitive Types due to the "Attempted to read or write protected memory" error.

ugh, all in all I like the model based concept, but I'm adding hours onto basic tasks
Apr 9, 2008 at 3:34 PM
  1. This is completly understandable and unfortunatelly this feature was not included in the factory not because of a limitation with DSL but of a lack of time in the project. However, nothing stops your from updating the package and add this feature. If you are interested in this, create a new thread and we'll help you to investigate on how to do it.
  2. Updating validation rules is not hard, in particular if you have the Extensibility Hands-on lab that shows how to do validation and extenend/update it. That way you may add more information to help you locate the error.
  3. This is something that should not happen in a normal case installation or for sure in 2008 version. I think that you might try this VS Hot fix to check if that solves your problem: that is also described in this thread:
Apr 10, 2008 at 2:27 PM
Edited Apr 10, 2008 at 4:48 PM
I'd like to echo amcool's sentiments and add my own little point of frustration with the WSSF - the DSL Integration Service. I don't know what's going on but now whenever I try to reference a datacontract from a service contract model I get the error message "Can't Access DSL Integration Service". I know the DIS package is installed as part of the WSSF install package so I have no idea what it's talking about. It's been really frustrating and with deadlines looming, it's becoming rather urgent that I fix this. So anyone with ideas, please help!

I'm working with VS2008 and I have the February 2008 edition of the WSSF:ME (binary) installed.
Apr 10, 2008 at 10:38 PM
Some reg keys may be the issue as describe this post: