DocProject Work Item Rss Feed

Created Issue: BadImageFormatException on New Project Wizard [33005]

DoughRamsey — Wed, 08 Aug 2012 16:22:26 GMT

I get a message box:

"An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)"

The application event log displays the following:

An error occurred while running the New Project Wizard:

System.BadImageFormatException: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)
at VSLangProj.References.AddProject(Project pProject)
at DaveSexton.DocProject.VSAnyProject.AddReference(Object projectReference)
at DaveSexton.DocProject.Wizards.ChooseSourcesStep.WizardFinished(WizardController controller)
at DaveSexton.DocProject.Wizards.Foundation.WizardStep.WizardFinishedInternal(WizardController controller)
at DaveSexton.DocProject.Wizards.Foundation.WizardController.<>c__DisplayClass9.b__8(WizardStep step)
at DaveSexton.DocProject.Wizards.Foundation.WizardController.ForEachStep(Action`1 action)
at DaveSexton.DocProject.Wizards.Foundation.WizardController.Finish(Boolean canceled)
at DaveSexton.DocProject.Wizards.Foundation.WizardForm.finishButton_Click(Object sender, EventArgs e)

I am running Windows XP, MS Visual Studio 2008, SP1 is installed.
This exception gets thrown whenever I try to add a DocProject to my C++ solution.

Commented Feature: Visual Studio 2010 Compatibility [25521]

davedev — Tue, 21 Feb 2012 13:34:26 GMT

Ensure DocProject is compatible with Visual Studio 2010.
Comments: ** Comment from web user: davedev **

Have you tried the latest version of SHFB? I believe it includes VS integration.

Commented Feature: Visual Studio 2010 Compatibility [25521]

Blackunknown — Tue, 21 Feb 2012 10:09:20 GMT

Ensure DocProject is compatible with Visual Studio 2010.
Comments: ** Comment from web user: Blackunknown **

Still hoping this will be done by some good citizen.

Commented Issue: Problem compiling .Net Compact Framework projects [31729]

dariosalvi78 — Tue, 15 Nov 2011 14:58:23 GMT

Hi,

I have a set of .Net Compact Framework, 3.5, projects I have included into a Sandcastle project.
In VS 2008 the compilation fails with not much information.
If I use the DocProject External UI I get this message: "The imported project C:\Windows\Microsoft.NET\Framework64\v3.5\Microsoft.CompactFramework.CSharp.targets was not found."

I have installed the .Net CF power toys, and I have that file in the 32bits version of the framework. How do I tell SandCastle to use the 32bits version???

Dario
Comments: ** Comment from web user: dariosalvi78 **

Sorry for the previou comment, I was translataing it and shortening the paths but for some reason I sent the comment before finishing :s

Thanks for the help

Dario

Commented Issue: Problem compiling .Net Compact Framework projects [31729]

dariosalvi78 — Tue, 15 Nov 2011 14:56:13 GMT

Hi,

In VS the log is the following:

Step 1 of 12: Change Directory

Changing current directory from "PATH\Documentation\Help\" to "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\Documentation\buildhelp"

Step 1 Time Elapsed: 00:00:00.0156256

Step 2 of 12: Execute MRefBuilder

C:\Program Files (x86)\Sandcastle\ProductionTools\MRefBuilder /config:"D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\Documentation\Help\Presentation\Style\Configuration\MRefBuilder.config" /out:reflection.org /internal- /dep:"C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll","C:\Windows\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll","C:\Windows\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll","C:\Windows\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll","C:\Windows\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll","C:\Windows\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll","C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll","C:\Windows\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll","C:\Windows\assembly\GAC_MSIL\Accessibility\2.0.0.0__b03f5f7f11d50a3a\Accessibility.dll","C:\Windows\assembly\GAC_MSIL\System.Runtime.Serialization.Formatters.Soap\2.0.0.0__b03f5f7f11d50a3a\System.Runtime.Serialization.Formatters.Soap.dll","C:\Windows\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll","C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll","C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll","C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\DesktopTestsLauncher\bin\Debug\DesktopTestsLauncher.exe" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\HSNDemo\bin\Release\HSNDemo.exe" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\HSN_Coordinator Bluetooth IMAGE\BTWrapper\bin\Release\BTWrapper.dll" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\HSN_Coordinator Bluetooth IMAGE\HSN_Coordinator\bin\Release\HSN_Coordinator.dll" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\PortableStationLibrary\bin\PDA\PortableStationLibrary.dll" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\PortableStationTests\bin\Debug\PortableStationTests.exe" "D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\PortableStation\bin\Debug\PortableStation.exe"

MrefBuilder (v2.6.10621.1)
Copyright ¸ Microsoft 2006
Error: A file access error occured while attempting to load the addin assembly 'D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\Documentation\Help\Presentation\Style\Configuration\MRefBuilder.exe'. The error message is: No se puede cargar el archivo o ensamblado 'file:///D:\Dario\Documentos\Proyectos\HeartCycle\Development\MainRepository\PortableStation\Documentation\Help\Presentation\Style\Configuration\MRefBuilder.exe' ni una de sus dependencias. El sistema no puede encontrar el archivo especificado.
Non-zero exit code: 1

Step 2 DaveSexton.DocProject.Engine.ExternalProcessException: Execute MRefBuilder:
The "C:\Program Files (x86)\Sandcastle\ProductionTools\MRefBuilder" process failed with exit code: 1.

Successful Steps: 1 of 12
Failed Steps: 1

Documentation help build failed.

Commented Issue: Problem compiling .Net Compact Framework projects [31729]

dariosalvi78 — Tue, 15 Nov 2011 14:46:18 GMT

Hi,

thanks very much for the answers !

AFAIK Compact Framework does not install 64 bits version of the .targets, there only exist the 32bits version.
I have checked the .project file under the Import element and I have this:

I guess the problem is this $(MSBuildBinPath).
I have changed it with the actual path in my computer which is C:\Windows\Microsoft.NET\Framework\v3.5 but then it starts asking the same for all the projects that I have included.

Is there some "elegant" way to modify it in a way that it would work on others' people computers and without changing the path to all the projects?

Thanks.

Dario

Commented Issue: Problem compiling .Net Compact Framework projects [31729]

davedev — Mon, 14 Nov 2011 19:09:46 GMT

I just found a related blog post: http://www.simonrhart.com/2010/06/automating-your-windows-mobile-6x.html

Seems like it's an issue with the Compact Framework not installing the .targets file into the correct directory on a 64 bit machine. I don't know why Visual Studio is able to resolve it though.

Commented Issue: Problem compiling .Net Compact Framework projects [31729]

davedev — Mon, 14 Nov 2011 19:03:55 GMT

You may want to set the log verbosity in Visual Studio to Normal or higher and also check the Windows Event Viewer under the Application log for error events with DocProject as the source. You should be able to gather more information about the failure in Visual Studio. See the documentation for more information on troubleshooting.

As for the error in the DocProject External UI, you can open your project file and change the path in the <Import> element to match. Though I'm surprised it doesn't work externally yet it works in Visual Studio. What path is in the <Import> element now?

Created Issue: Problem compiling .Net Compact Framework projects [31729]

dariosalvi78 — Mon, 14 Nov 2011 10:28:10 GMT

Commented Issue: Topic Management Form Couldn't be displayed in main monitor after switch dual monitors to single monitor. [25509]

salsailor — Sat, 02 Apr 2011 00:15:15 GMT

Yesterday, I cann't open topic management form from docproject properties page. I found it caused by dual monitor display. Here are detail steps:
1. Display Visual Studio 2008 in secondary monitor.
2. Open docproject properties page and click topic managment.
3. Modal form of Topic management is displayed in secondary monitor too.
4. Close all applications and restart computer in single monitor model. (Or just switch dual monitors display to single monitor display)
6. Open Visual Studio again and try to open Topic management Form.
7. No modal form displayed and Visual Studio lost response to any mouse input.
8. Switch single monitor display to dual monitor display.
9 The topic management form displayed in secondary monitor.
Comments: ** Comment from web user: salsailor **

Dave, thanks for the quick response. That works. The dialog is hidden to the leftest side of my screen, maybe it's because once a upon a time I had two monitors and that's where it remembers its last location.

Lee

Commented Issue: Topic Management Form Couldn't be displayed in main monitor after switch dual monitors to single monitor. [25509]

davedev — Fri, 01 Apr 2011 09:20:45 GMT

Correction: #5. "Top" was supposed to be "Tap", as in "Tap one of the arrow keys on your keyboard..."

Commented Issue: Topic Management Form Couldn't be displayed in main monitor after switch dual monitors to single monitor. [25509]

davedev — Fri, 01 Apr 2011 09:19:17 GMT

Try the following as a workaround. Note that I haven't tested this myself:

1. Open the Topic Designer dialog, although you can't see it because it's off-screen.
2. Press Alt+Space once to open the dialog's system menu, which is also probably going to be off screen.
3. Press the M key. Your mouse pointer should change to the move cursor.
4. Without pressing any buttons, move your mouse into the center of your screen. The pointer is still the move cursor.
5. Top one of the arrow keys a few times until the dialog appears on your screen. You should now be able to drag it by the title bar.

Commented Issue: Topic Management Form Couldn't be displayed in main monitor after switch dual monitors to single monitor. [25509]

salsailor — Fri, 01 Apr 2011 02:02:52 GMT

I am having a similar problem. The "Topic Explorer' works but the "Topic Designer" will lock up VS2008. It is no where to see, I can "hear" the modal dlg is somewhere, but it's hidden, no way to bring it up regardless how many montiro I have. I can hide the whole desktop, it is still hidden. So the Visual Studio is locked up and I have to kill it from taskmanager.

I am useing VS2008 with PlugIn 1.11.0

Commented Feature: Visual Studio 2010 Compatibility [25521]

JohaViss — Tue, 23 Nov 2010 08:36:51 GMT

Ensure DocProject is compatible with Visual Studio 2010.
Comments: ** Comment from web user: JohaViss **

I have over a dozen projects that needs upgading to VS2010.

For a first version, I don't need anything more than currently available. Just a VS2010 version.
If no one is going to upgrade this project, please release the sources so that we can try to upgrade it ourselfs.

Commented Feature: Visual Studio 2010 Compatibility [25521]

FredrikRofors — Thu, 12 Aug 2010 06:48:38 GMT

Ensure DocProject is compatible with Visual Studio 2010.
Comments: ** Comment from web user: FredrikRofors **

Looking forward to VS 2010 support...

Commented Issue: Check Dialog Window Position for Current Monitor Setup [28328]

TonyGravagno — Fri, 30 Jul 2010 05:44:24 GMT

Original discussion: http://docproject.codeplex.com/Thread/View.aspx?ThreadId=221785

Check each dialog's saved position against the current monitor setup before displaying the dialog. If the position will be off-screen, default to center screen and save the new coordinates.

Due to multi-monitor support, negative position values must still be acceptable; i.e., off-screen detection is not as trivial as excluding negative values and large positive values, so there must be some way to query the environment to know whether a specified screen position will actually be visible or not.
Comments: ** Comment from web user: TonyGravagno **

I'm running a server, not laptop, sometimes with one monitor and other times with two. I don't think "the case of the disappearing window" is a big deal as it could happen with any window of any application - and a Google on the topic returns enough hits to show that this situation isn't unusual. I believe there is some function to center forms on the current window space. Even simpler would be a hardcoded x=100, y=100. For our purposes with DocProject I can't see why that would be a problem.

Thanks for your efforts.

Created Issue: Check Dialog Window Position for Current Monitor Setup [28328]

davedev — Fri, 30 Jul 2010 04:20:47 GMT

Commented Issue: x64 installation bug [17410]

retrotom — Thu, 29 Jul 2010 17:00:23 GMT

When you install DocProject v 1.11.0 RC on an x64 machine, it creates the following registry entry:
Comments: ** Comment from web user: retrotom **

I'm having the same issue. As the previous comment pointed out, this is because of the mismatch in the installer and the external ui application. The external UI project is set to compile as AnyCPU -- so it executes as 64-bit process and can only access the 64-bit registry. The Installer is a 32-bit application (x86) and therefore creates the registry keys in the 32-bit registry. The Installer should be changed to be AnyCPU or ExternalUI compiled as x86 instead of AnyCPU.

Commented Feature: DocSite is "uglier" in Firefox & Chrome [28255]

davedev — Mon, 26 Jul 2010 07:57:05 GMT

The default DocSite style "BasicBlue" is missing the it's gradients in Firefox and Chrome. See the attached picture or try the live DocSite at http://www.unitypark3d.com/support/

Tested on Firefox 3.6.7, Chrome 5.0 and Internet Explorer 8.0.
Comments: ** Comment from web user: davedev **

Thanks, this looks like it will be helpful.

Commented Feature: DocSite is "uglier" in Firefox & Chrome [28255]

SpiderMaster — Sat, 24 Jul 2010 20:00:40 GMT

Your code for this feature if you wish to research more!
progid:DXImageTransform.Microsoft.Gradient(startColorStr=#FFFFFFFF, endColorStr=#FFCBDEFF, gradientType=1); COLOR: #ababab

As far as what I have learnt this feature is not supported by other browsers or in fact other operating systems other than those by microsoft due to the nature of how the gradient is applied accessing the native library programmatically through the IE Browsers on a client machine with the library installed. You may also find that this wont work with Graphics Properties set to maximum performance.

So really at the end of the day its a feature not supported by much at all and there is not much that can be done about it apart from enjoying the benefit while in IE or since I feel generous you can have my code, Its not complete for what your doing as I dont use DocProject but you can soon work out what needs done with it.

#gradient {

/* For WebKit (Safari, Google Chrome etc) */
background: -webkit-gradient(linear, left top, left bottom, from(#00f), to(#fff));

/* For Mozilla/Gecko (Firefox etc) */
background: -moz-linear-gradient(top, #00f, #fff);

/* For Internet Explorer 5.5 - 7 */
filter: progid:DXImageTransform.Microsoft.gradient(startColorstr=#FFFFFFFF, endColorstr=#FFFFFFFF);

/* For Internet Explorer 8 */
-ms-filter: progid:DXImageTransform.Microsoft.Gradient(startColorStr=#FFFFFFFF, endColorStr=#FFCBDEFF, gradientType=1); COLOR: #ababab
}