Can anyone please tell me what I am going wrong. What is the best way to
deploy web part in an environmental that consists of multiple front end web
servers.
Thanks
It seems you met some problem when try deploying your well developed
webpart controls.
As you mentioned the features, are you deploying them as features mentioned
in the following article?
#Deploying web parts as a feature
http://sharepointnutsandbolts.blogspot.com/2007/05/deploying-web-parts-as-fe
ature.html
For general test, I suggest you try a simplified webpart and also deploy it
manually to see whether it works:
#Writing Custom Webparts for Sharepoint 2007
http://blah.winsmarts.com/2006/05/14/writing-custom-webparts-for-sharepoint-
2007.aspx
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Rafia Tapia" <delt...@nospam.nospam>
Subject: deploying webpart on two front end web server
Date: Wed, 30 Jan 2008 22:00:46 -0500
"Steven Cheng[MSFT]" <stc...@online.microsoft.com> wrote in message
news:l2eCUM$YIHA...@TK2MSFTNGHUB02.phx.gbl...
I'm still doing my deployments by hand (crafting XML by hand and so
forth) so I don't know what VSS is doing for you in that batch file.
It seems that there should be some intermediate output, probalby some
kind of failure message when it tries to install the feature.
Can you share any more detail from that process? Is there any kind of
log file you can post?
--Paul Galvin, Conchango
RSS @ http://feeds.feedburner.com/PaulGalvinsSharepointSpace
Web site @ http://paulgalvin.spaces.live.com
So manually install webpart works, there might be something got incorrect
in the feature based deployment. Have you tried a simplified scenario that
create a single standard webpart and deploy it into the SPS server? I'm
wondering whether this is a specific case or a common problem that might be
related to the SPS server.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Rafia Tapia" <delt...@nospam.nospam>
References: <us1y3W7Y...@TK2MSFTNGP02.phx.gbl>
<l2eCUM$YIHA...@TK2MSFTNGHUB02.phx.gbl>
Subject: Re: deploying webpart on two front end web server
Date: Thu, 31 Jan 2008 11:02:54 -0500
I also want to know what is the best practise for deploying web parts in a
farm environment. The way I tried to do it through Visual studio was that
each of the webpart is a feature and then created a solution (.wsp) that
would install and activate the features. One of things I am not sure how it
would work in farm deployment is that when I add and delpoy the solution
using stsadm utility, would it put my webpart dll on all the front end web
server's GAC and would it also change the web.config file on all the front
end servers.
"Steven Cheng[MSFT]" <stc...@online.microsoft.com> wrote in message
news:U4pOrGK...@TK2MSFTNGHUB02.phx.gbl...
<galvi...@gmail.com> wrote in message
news:fc686aff-1223-4058...@q21g2000hsa.googlegroups.com...
As for front-end multiple virtual server scenario, when you deploy webpart
packages through stsadm.exe ,I think you'll need to do the deploy for each
of those virtual servers(no matter whether they've shared the same
persistence database or not).
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: "Rafia Tapia" <delt...@nospam.nospam>
Subject: Re: deploying webpart on two front end web server
Date: Mon, 4 Feb 2008 12:41:16 -0500
How is everything going?
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: stc...@online.microsoft.com (Steven Cheng[MSFT])
Organization: Microsoft
Date: Tue, 05 Feb 2008 07:48:09 GMT