Re: Web Part deployment

From: BentleyInc (BentleyInc_at_online.nospam)
Date: 12/09/04


Date: Thu, 9 Dec 2004 07:16:53 -0500

IMO, MSFT missed the ball on this one. The package deployment process for
Simple controls is great. I sure hope there is going to be better support
for more complex solutions in the future.

However, why doesn't this work. In my manifest file I specify two DLLs that
should end up in the bin directory. Bentley.PW.SharePoint.WebParts.dll has
the actuall web parts in it. The Bentley.ECOM.dll is a support DLL for the
webparts dll. When I run STSADM only the Bentley.SharePoint.WebParts.dll is
copied to the BIN directory. I have verified that BOTH DLLS are in the CAB
file.

<?xml version="1.0"?>
<!-- You need only one manifest per CAB project for Web Part Deployment.-->
<!-- This manifest file can have multiple assembly nodes.-->
<WebPartManifest xmlns="http://schemas.microsoft.com/WebPart/v2/Manifest">
  <Assemblies>
    <Assembly FileName="Bentley.ECOM.dll">
    <Assembly FileName="Bentley.PW.SharePoint.WebParts.dll">
        <!-- Use the <ClassResource> tag to specify resources like image
files or JScript files that your Web Parts use. -->
    <!-- Note that you must use relative paths when specifying resource
files. -->
      <ClassResources>
        <ClassResource FileName="images\nav_next.gif"/>
      </ClassResources>
      <SafeControls>
          <SafeControl Assembly="Bentley.PW.SharePoint.WebParts"
Namespace="Bentley.PW.SharePoint.WebParts" TypeName="*" Safe="True" />
      </SafeControls>
    </Assembly>
  </Assemblies>
  <DwpFiles>
    <DwpFile FileName="Bentley.PW.SharePoint.WebParts.Content.dwp"/>
    <DwpFile FileName="Bentley.PW.SharePoint.WebParts.GUITest.dwp"/>
    <DwpFile FileName="Bentley.PW.SharePoint.WebParts.Navigation.dwp"/>
    <DwpFile FileName="Bentley.PW.SharePoint.WebParts.Properties.dwp"/>
    <DwpFile FileName="Bentley.PW.SharePoint.WebParts.Publisher.dwp"/>
  </DwpFiles>
</WebPartManifest>

my makecab DDF file looks like
;*** Sample Source Code MakeCAB Directive file example
;
.OPTION EXPLICIT ; Generate errors
.Set CabinetNameTemplate=PWWebParts.cab
.set DiskDirectoryTemplate=CDROM ; All cabinets go in a single directory
.Set CompressionType=MSZIP;** All files are compressed in cabinet files
.Set UniqueFiles="OFF"
.Set Cabinet=on
.Set DiskDirectory1=.
Manifest.xml
wpcatalog\Bentley.PW.SharePoint.WebParts.Content.dwp
wpcatalog\Bentley.PW.SharePoint.WebParts.GUITest.dwp
wpcatalog\Bentley.PW.SharePoint.WebParts.Navigation.dwp
wpcatalog\Bentley.PW.SharePoint.WebParts.Properties.dwp
wpcatalog\Bentley.PW.SharePoint.WebParts.Publisher.dwp
bin\Bentley.PW.SharePoint.WebParts.dll
..\ecom\Bentley.ECOM.dll
.Set DestinationDir=images
wpresources\Bentley.PW.SharePoint.WebParts\Images\nav_next.gif
;*** <the end>

"Wei-Dong XU [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
news:AgsxY2M3EHA.3436@cpmsftngxa10.phx.gbl...
> Hi Marcus,
>
> I understand your scenario; you are going to control the installation
> procedure to deploy dll and images to different location with the
> installation of web part.
>
> As the suggestion from Jeff, you can use the VS.net installer for this or
> write the MSI script for the deployment.
>
> " can't use the stsadm.exe tool to deploy to remote servers, etc "
> I'd suggest you can write one script file(VBS/JS) to call the stsadm. This
> exe file is located at the location:
> %programfiles%\Common Files\Microsoft Shared\web server
> extensions\60\bin\stsadm.exe
>
> Then from the MSI script or VS.net installer, you can call this script
file
> to perform the deployment operation.
>
> In addition, you can also try one 3rd party installation tool
InstallShield:
> http://www.installshield.com/
>
> Please feel free to let me know if you have any question.
>
> Best Regards,
> Wei-Dong XU (WD.XU)
> Microsoft Product Support Services
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> ---
> This response contains a reference to a third party World Wide Web site.
> Microsoft is providing this information as a convenience to you. Microsoft
> does not control these sites and has not tested any software or
information
> found on these sites; therefore, Microsoft cannot make any representations
> regarding the quality, safety, or suitability of any software or
> information found there. There are inherent dangers in the use of any
> software found on the Internet, and Microsoft cautions you to make sure
> that you completely understand the risk before retrieving any software
from
> the Internet.



Relevant Pages

  • RE: Default Website - Best Practise?
    ... website installation and setting back to the original site ID when the ... deleting the default web site is not recommended. ... Microsoft Online Community Support ...
    (microsoft.public.inetserver.iis.security)
  • RE: .jpg .gif .bmp file associations gone, upgrade from Office XP
    ... Microsoft Online Partner Support ... Microsoft technology partners in the United States and Canada. ... >You can re-install Photo Editor on all the systems. ... >rolling out an office installation through current methods and only ...
    (microsoft.public.office.setup)
  • Re: Office 2007 Conversion - exisiting educational site license
    ... licensing issues and support can be a nightmare! ... replacement installation media and product keys, Microsoft won't help. ... Once I cut out the middle-man (the OEM) I've been much happier with support ...
    (microsoft.public.office.misc)
  • Security Update, February 13, 2002 (MSXML 4.0)
    ... give me any support however. ... >I thought that Microsoft supported security issues. ... >emailed a request and sent them my installation history. ... >indicates that your copy of Windows Me was purchased ...
    (microsoft.public.security)
  • RE: GetBinaryType not working for DLLs
    ... If you really wanted to distinguish between Exe and DLL, ... Based on the Microsoft PE and COFF ... Microsoft Online Community Support ...
    (microsoft.public.win32.programmer.tools)