Re: Evaluating D2005: no change on save

Leonel wrote:

No work around as was provided for D8 (in the registry)? 


Sorry, I don't know what workaround is that. If it works for D8 it
might still work for D2005. Did you try it?


It was adding a value in the registry
HKEY_CURRENT_USER\Software\Bor­land\BDS\3.0\AspDebuggingOptio­ns\General]
"SaveMarkupAsIs"="1"

I tried it a while ago and it didn't work.
But I can't remember if I used DCM then, so it is possible I put it in the wrong place (should go in de HKEY_CURRENT_USER\Software\Bor­land\DCM secion in that case.

I'm going to make a testobject because I haven't got any objects anymore that the D2005 designer can parse.

More on that later

Sting
.

Relevant Pages

  • Inherited forms in CF2 VS2005 cant compile
    ... I am using form inheritance in VS2005 professional and all was going well - ... when I added a reference to System.Data.SqlServerCe it now causes ... "DesktopCompatible" workaround (i.e. through the class designer). ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Form is not displayed at the correct (designer) size.
    ... The workaround is not so "very simple" because the workaround you are ... The programmer designs a form using the designer. ... > Form.Size calling in place of Form.ClientSize code statement. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.vstudio.general)
  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.dotnet.framework)
  • 1.0 vs 1.1 framework conflict in VStudio
    ... In my properties of my project in the references path, ... The designer inspected the ... The workaround is to reference v1.0 first, ... do this I cannot compile because there are some v1.1 features I need, ...
    (microsoft.public.vsnet.general)