ANS-Denver

PrintForm works on my development workstation in both IDE & the application EXE installed from ClickOnce site. However, on 2 client PCs, both running Windows XP, the EXE fails with "Could not load file or assembly 'Microsoft.VisualBasic.PowerPacks.Printing.PrintForm, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified."

  • During ClickOnce install:
    • No errors. In fact, I can find no install log in C:\WINDOWS\Temp\Temporary Internet Files afterwards.
    • No signing.
    • No elevated permissions.
  • gacutil finds Microsoft.VisualBasic.PowerPacks.Printing.PrintForm on my development workstation, but does not find it on a client PC.
  • the exe.manifest file contains <dependency>
    <dependentAssembly dependencyType="install" allowDelayedBinding="true" codebase="Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll" size="29552">
    <assemblyIdentity name="Microsoft.VisualBasic.PowerPacks.Printing.PrintForm" version="1.0.0.0" publicKeyToken="B03F5F7F11D50A3A" language="neutral" processorArchitecture="msil" />
    <hash>
    <dsig:Transforms>
    <dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
    </dsig:Transforms>
    <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
    <dsig:DigestValue>41WXRz1IGIwd1RFxUFBCl0rkGgE=</dsig:DigestValue>
    </hash>
    </dependentAssembly>
    </dependency>
  • In my project, the reference to Microsoft.VisualBasic.PowerPacks.Printing.PrintForm:
    • Copy Local = True
    • Specific Version = True

What am I missing




Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

Scott Tucker

Are you using the .deploy feature In the Publish Page look in the Options dialog, and see if the 'use ".deploy" file extension checkbox is checked. If you are not, does your IIS site block .dll files

When you look in the ClickOnce local application store (%userdirectory%\Local Settings\App\2.0\ ) do you see the PowerPacks dll in the same directory as the applications

Thanks,

Scott Tucker

Microsoft Visual Basic Team





Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

"Use '.deploy' file extension" is checked, and in the version's directory on the Publishing Location (name=LifeCompassApplier_1_0_1_5), the file is named "Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll.deploy". By "your IIS site block .dll files", that would be the IIS at the Publishing Location, yes In this case, it's a hosting facility, so I'd have to check, but that's not the issue, right

In "C:\Documents and Settings\Administrator\Local Settings\Apps\2.0\QXWWC7EP.33G\5HCANOMY.RGE\life..tion_c7431be139569a3a_0001.0000_e16960124ae61d10", dated 02/13/07 matching my last try at this, we see:

02/14/07 16:30 <DIR> .
02/14/07 16:30 <DIR> ..
02/14/07 16:30 0 dir.list
02/13/07 18:13 <DIR> Help
02/13/07 18:13 2,944 Interop.Excel.cdf-ms
02/13/07 18:13 1,093,632 Interop.Excel.dll
02/13/07 18:13 988 Interop.Excel.manifest
02/13/07 18:13 2,000 Interop.Office.cdf-ms
02/13/07 18:13 155,648 Interop.Office.dll
02/13/07 18:13 617 Interop.Office.manifest
02/13/07 18:13 2,932 Interop.Word.cdf-ms
02/13/07 18:13 655,360 Interop.Word.dll
02/13/07 18:13 986 Interop.Word.manifest
02/13/07 18:13 5,640 LifeCompassApplier.cdf-ms
02/13/07 18:13 3,379,200 LifeCompassApplier.exe
02/13/07 18:13 48,340 LifeCompassApplier.exe.cdf-ms
02/13/07 18:11 3,253 LifeCompassApplier.exe.config
02/13/07 18:13 26,377 LifeCompassApplier.exe.manifest
02/13/07 18:13 2,080 LifeCompassApplier.manifest
01/22/07 15:16 2,408 Microsoft.Vbe.Interop.cdf-ms
01/22/07 15:16 64,088 Microsoft.Vbe.Interop.dll
01/22/07 15:16 819 Microsoft.Vbe.Interop.manifest
01/17/07 09:10 3,996 Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.cdf-ms
01/17/07 09:10 29,552 Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll
01/17/07 09:10 1,474 Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.manifest
01/22/07 15:16 2,444 office.cdf-ms
01/22/07 15:15 223,800 Office.dll
01/22/07 15:16 791 office.manifest
02/13/07 18:13 <DIR> Resources
25 File(s) 5,709,369 bytes
4 Dir(s) 129,974,669,312 bytes free


Also, Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll & Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.xml reside in the project's bin directory, under Release & Debug as well as under the .publish directories in both of those.






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

In the Publishing Location, LifeCompassApplier_1_0_1_5, we see:

02/14/07 16:33 <DIR> .
02/14/07 16:33 <DIR> ..
02/14/07 16:33 34 dir.list
02/13/07 18:01 <DIR> Help
02/13/07 18:00 1,093,632 Interop.Excel.dll.deploy
02/13/07 18:00 155,648 Interop.Office.dll.deploy
02/13/07 18:00 655,360 Interop.Word.dll.deploy
02/13/07 18:00 3,253 LifeCompassApplier.exe.config.deploy
02/13/07 18:01 3,379,200 LifeCompassApplier.exe.deploy
02/13/07 18:01 26,377 LifeCompassApplier.exe.manifest
02/13/07 18:01 64,088 Microsoft.Vbe.Interop.dll.deploy
02/13/07 18:01 29,552 Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll.deploy
02/13/07 18:01 223,800 Office.dll.deploy
02/13/07 18:01 <DIR> Resources
10 File(s) 5,630,944 bytes
4 Dir(s) 18,226,692,096 bytes free






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

I also tried the install logged on as explicit Administrator, instead of a user with Administrator privileges: that did not work either.




Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

shoagMSFT

The following topic explains the IIS configuration issues:

http://msdn2.microsoft.com/en-us/library/ms228998(VS.80).aspx

Hope this helps,

Steve Hoag

Microsoft Visual Basic






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

That article says an error will result if IIS is blocking the download of particular file(s). In my case, no error occurs: the install runs to completion, the application runs, but no PrintForm dll has been installed; that lack expresses itself only when the EXE tries to use PrintForm functionality.




Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

shoagMSFT

Actually, what it says is "If a user attempts to run a ClickOnce application that accesses a blocked file on a Web server, an error will result." I take that to mean that the error will occur at run time, not during installation.




Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

Is there a log created during the deployment that indicates blocked files If so, where is it

If my kit contains files named like Microsoft.VisualBasic.PowerPacks.Printing.PrintForm.dll.deploy, will IIS figure out it's a DLL & block it






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

shoagMSFT

As far as I know ClickOnce doesn't create a log.

What happens if you try to publish via a different method - on a file share or on a CD If you can successfully publish via one of those methods, then the IIS configuration is the problem.

Also, what files are getting published to the local machine where it doesn't run Are you seeing the other .dll's specified in your manifest






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

My hosting company does discourage downloading any executable files, regardless of name, noting:

  • most all networks block these files by Email, lots of users firewalls will block these types as well
  • Your server (our server) does not have restrictions on sending them - you can download dll's from your site - but results will vary on the machines trying to receive them... and there is no MIME type set for them

So, I will have to turn away from ClickOnce & go to Windows Installer.

How do I designate PrintForm in a Setup project






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

shoagMSFT

You don't have to do anything special. As long as the PrintForm component is referenced in your project, the Setup and Deployment project will automatically detect the dependency and include the file.




Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

tabdalla

I have the PrintForm component referenced in my project and ClinkOnce is not automatically detecting the dependency and including the file for deployment. I've been installing the PrintForm component first, outside of the ClickOnce deployment, as a workaround until I created a custom bootstrapper. But, if ClickOnce should be automatically detecting the dependency and including it as a prerequisite, any ideas on why it's not showing up in the prerequisite dialog box even though it's referenced

Thanks,

Tony






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

Tony/tabdalla:

  1. Find Properties for Project for application (as opposed to the Setup Project): in Solution Explorer, right-click the Project & choose Properties from context menu; not the Properties floating toolbar, the 1 that goes with Solution Explorer.
  2. On Properties window, click References.
  3. On References, find Microsoft.VisualBasic.PowerPacks.Printing.PrintForm & open Properties, this time the Properties floating toolbar.
  4. Set Copy Local to true.

I provide all the detail on how to get there because many explanations assume you know the IDE like the back of your hand; since I do not, I end up spending a long time just figuring out where to go to set these things.






Re: Visual Basic Power Packs PrintForm does not Install via ClickOnce Deployment

ANS-Denver

shoagMSFT:

Re "You don't have to do anything special. As long as the PrintForm component is referenced in your project, the Setup and Deployment project will automatically detect the dependency and include the file."

True, but once you started the Setup and Deployment Project, you then have to:

1. start the File System editor (View>Editor>File System)
2. select Application Folder
3. right-click & from context menu, select Add>Project Output

then & only then, does PrintForm show up in what gets built.

Then there's the "Content Files from". I spent time wishing the project would just copy the contents of my Help directory; finally discovered that that's what "Content Files from" does.

Thanks for your help. My Windows Installer does nearly everything I want it to, including install the PrintForm & other DLLs, like office, MSWORD, & EXCEL.

However, I cannot figure out how to add another shortcut, 1 that points to a tutorial HTML file, to User's Program Menu, in the application's group I created. Easy to get the shortcut to the EXE (in the the File System editor, Add>Project OUtput), but "Create Shortcut to ..." doesn't want to be changed as far as target. Do I Add>File Same process would include ReadMe.txt &c.