The ever present, Chee Wee Chua, reminded me of something that you may have already encountered with yesterday's fix. Be sure you run sn -Vr on the Borland.Studio.Vcl.Design.dll assembly. That will disable strong-name validation for that assembly so that it will load properly. Thanks, Chee Wee! Duh! If that doesn't fix it, you can simply not install the Borland.Studio.Vcl.Design.dll assembly until I can figure out how to get it strong-named... I guess I'll have to see about grabbing our strong name private key from the integration team.
Update: I've now strong named the Borland.Studio.Vcl.Design.dll assembly and updated the d2005_update.zip file. You'll need to re-download this file.
Udpate 2: There is now a CodeCentral entry that has these updates. I'll probably be removing the files from homepages.borland.com in a few days in favor of using CodeCentral.
Update 3: Ok... for now, ignore the Borland.Studio.Vcl.Design.dll assembly until I can get the assembly version number garbledygook figured out.
After installing this patch, I get the following error when I start a vcl.net project:
ReplyDeleteError creating form: Could not load type Borland.Studio.ToolsAPI.IOTASortableStructureNode from assembly Borland.Studio.ToolsAPI, Version = 9.0.1882.30496, culture=neutral, PublicKeyToken=91d62ebb5b0dab16
I can't view the form in design mode, only code.
Many Thanks!!!
ReplyDelete...and please keep fixing :-)
For now, don't install the Borland.Studio.Vcl.Design.dll assembly until I can get the assembly version stuff straightened out.
ReplyDeleteJust wanted to comment on the fact that I had to revert the Borland.Studio.Vcl.Design.dll to the original one. With the new one, I got an "instance not set to an object" (or whatever the exact text was) error for each form, and I could not design any VCL.NET forms.
ReplyDeleteBut I see you already found that.
how to install that updating?substitu-the the direct files in the paste?how to proceed?help me plix =D
ReplyDeleteit would like an explanation step the step possible case ^.-
ReplyDeleteUnzip it (all but the mentioned Borland.Studio.Vcl.Design.dll) in the Bin dir of your Delphi install.
ReplyDeleteBackup the originals in case you decide to rollback.
Thiago,
ReplyDeleteAllen provided some detailed instructions with the first patch he announced in August. Use those instructions for each file contained in this roll-up fix but don't install Borland.Studio.Vcl.Design.dll yet. Don't worry about the FastMM unofficial patch mentioned in this earlier blog as one of the latter patches from Allen removes the need for it.
Here's the url:
http://blogs.codegear.com/abauer/archive/2005/08/05/20641.aspx
Alan,
ReplyDeleteDid you ever manage to figure our the Assembly Versioning Number debacle?
Thanks,
Mark
The FastMM4 has many compiler/debug options. Will Borland release a Debug version of it in DeXter? Which switches will be used?
ReplyDeleteCould you please fix Copy/Paste on a Multi-Monitor System, where the main IDE is on one screen and the Tool Palette/Obj Inspector/Structure are on another.
ReplyDeleteDelphi 2005 "Update 4"
Thanks