Shared solution corruption

Jaspal Hayre

Hi All

 

Having a strange issue. Myself and another developer in a different time zone are using a virtual machine to develop a solution at different times. What we are finding is that when he saves the solution at the end of his day and I open it I get a load of validation errors and when I create / update a solution and save at the end of my day he gets validation errors when he opens the solution (we dont get the errors when we open ourselves).

 

Typicall errors we get are:

DateTime is an ambiguous reference between Metastorm.Runtime.Types.DateTime

 

and

 

The type or namespace '****' could not be found (are you missing a using directive or an assembly?)

 

I think it might be regional settings issue as we also had a funny testing dates and times whereby when he used RDC to get on the VM and tested a solution, when he entered a date on a form it would save in the DB with a date one day prior to what he selected!

 

So if he entered 30/01/12 the date in DB would be 29/01/12. We got round this by changing the timezone on his machine but this has not fixed issues with sharing solution files!

 

Thanks

Jas

Tony Wheeler

Hi Jas,

 

The errors don't sound like they're related to the timezone, but you may be doing scripting with DateTimes because of this.

 

There is a Metastorm type (Metastorm.Runtime.Types.Datetime) of the same name as the .Net type DateTime (System.DateTime). Server side scripts can get confused if you have the .Net namespace activated alongside using the Metastorm Types. I would suggest explicitly defining your types inline if you must use both namespaces alongside each other and be sure that any operation you are doing against a Metastorm control is with Metastorm.Runtime.Types.Datetime... not a System.DateTime.

 

The other errors of missing namespaces is kind of a red herring. If you have a problem in server side scripts, you can get several of those warnings. Generally, on validation if you get 100 errors, look for the outlier. Most of the time, fixing the error that's by itself in the validation list will get rid of all the missing namespace errors.

 

After verifying the DateTime types you are using in code, if problems persist, please send an email to the HelpDesk.

Jaspal Hayre

Just a quick up date on this. My bad for reporting this as a corruption. Should have investigated it a bit more. I tried numerous things like clearing out the various designer related directories etc but nothing appeared to work so I started looking into the errors in the Solution provided by my colleague and it was indeed using DateTime without fully qualifying i.e. was using DateTime.CurrentDate and needed to use Metastorm.Runtime.Types.Datetime.CurrentDate and had some incorrect variable declarations in serverside scripts.

 

I'm still confused though why he could open the solution, validate and deploy without getting these errors? will have to investigate that at another time!