|
Stan S
Posts: 184
Joined: 2007-09-04
|
I am upgrading my projects to ADX for .NET 2010 Beta 1.
When I rightclick at project node and choose "Create Setup Project", for some projects it works just fine, however for most projects it gives the following error
Detailed technical information follows:
---
Application Domain: DefaultDomain
Assembly Codebase: file:///C:/Program Files/Add-in Express/Add-in Express for .NET/Bin/Packages/VS2005/AddinExpress.Wizard.dll
Assembly Full Name: AddinExpress.Wizard, Version=6.0.3037.2005, Culture=neutral, PublicKeyToken=4416dd98f0861965
Assembly Version: 6.0.3037.2005
Assembly Build Date: 25.04.2008 02:06:50
Exception Source: mscorlib
Exception Type: System.ArgumentException
Exception Message: The path is not of a legal form.
Exception Target Site: NormalizePathFast
---- Stack Trace ----
System.IO.Path.NormalizePathFast(path As String, fullCheck As Boolean)
AddinExpress.Wizard.dll: N 0000 (0x0) IL
System.IO.Path.NormalizePath(path As String, fullCheck As Boolean)
AddinExpress.Wizard.dll: N 0015 (0xF) IL
System.IO.Path.GetDirectoryName(path As String)
AddinExpress.Wizard.dll: N 0009 (0x9) IL
AddinExpress.SetupWizard.SetupWizardForm.CreateSetupProject(primaryOutputPath As String)
AddinExpress.Wizard.dll: N 0175 (0xAF) IL
AddinExpress.SetupWizard.SetupWizardForm.CreateSetupProject(project As Project)
AddinExpress.Wizard.dll: N 0045 (0x2D) IL
AddinExpress.Wizard.ADXPackage.Exec(guidCmdGroup As Guid&, cmdID As UInt32, nCmdexecopt As UInt32, pvaIn As IntPtr, pvaOut As IntPtr)
AddinExpress.Wizard.dll: N 0655 (0x28F) IL
-----------
I can give you exact paths of projects via email, as they contain names of my clients which is confidential information.
Both "successful" and "unsuccessful" path only have letters and "!" sign, no spaces. They all are in subfolders of d:\!work, so they all have "!" sign in path.
I noticed that if I copy project to "projectname_1" folder, so it has underscore, open that project from new path alone and "Create setup project", it works fine so far. |
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Stan.
Yes, please send me the paths and a problematic project (if possible) via e-mail. I will test it. |
|
|
Stan S
Posts: 184
Joined: 2007-09-04
|
|
Just discovered workaround. If I rename SLN file by merely adding "2" (mysolution.sln -> mysolution2.sln), the Create Setup wizard works just fine. Tested it on a couple of problematic projects, always worked for me. So, no action necessary at this point. |
|
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
|
Thanks for letting us know, Stan. |
|
|
rob
Posts: 4
Joined: 2010-04-15
|
this work-around worked for me as well.
I'm using VS 2010 and am targeting the .NET framework 2.0 for an IE plugin. |
|
Forums
Topics
Search
Help
Login
Register