Sometimes, even though the orchestration does not show any error , when you build your project, you get a lot of them and when double-clicking the error it shows you something perfectly normal.
You can close VS ten times but it doesn’t help…
This thing drove me crazy for a while until I knew what to do.
What do you do then?
Well, you know the orchestration is formed of 2 parts, right?
One is XML of type <om:MetaModel xmlns:om=”http://schemas.microsoft.com/BizTalk/2003/DesignerData”/> and the other is in X# (or Xlang if you want).
If you look at the Xlang part, you’ll see that your error is showing there instead of the relevant piece of code. However, in the XML, the code appears and not the error.
The conclusion is that it’s the XML part that builds the Xlang part and not the opposite.
Great! Now what?
Edit the orchestration, get rid of the second one (basically everything below the #endif // __DESIGNER_DATA line), when rebuilding the project, it will behave as normal – showing no errors (provided that you really don’t have any error there).
Now if after building you open your orchestration with the XMLEditor (right click -> open with -> XMLEditor), you’ll see that the Xlang part has not been generated…
The thing is that the X# won’t be generated unless you change something in the orchestration.
Just open any shape like an expression shape and add a random space anywhere and that will do the trick.
Edit again and you’ll see the X#.
#if __DESIGNER_DATA#error Do not define __DESIGNER_DATA.<?xml version=“1.0“ encoding=“utf-8“ standalone=“yes“?>
<om:MetaModel MajorVersion=“1“ MinorVersion=“3“ Core=“2b131234-7959-458d-834f-2dc0769ce683“ ScheduleModel=“66366196-361d-448d-976f-cab5e87496d2“ xmlns:om=“http://schemas.microsoft.com/BizTalk/2003/DesignerData“>
…</om:MetaModel>
#endif // __DESIGNER_DATA <– Everything below this line should be removed
[Microsoft.XLANGs.BaseTypes.BPELExportable(false)]
module xxxxxxxxxxxxxxxxx
{
