By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,110 Members | 990 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,110 IT Pros & Developers. It's quick & easy.

web parts for sharepoint services and portal

P: n/a
if i created a web part in vs.net like http://www.devx.com/dotnet/Article/17518/0/page/2 is it possible to use the web part in both the sharepoint services environment and the sharepoint portal environment without modification

new to these products and not sure where to look for resource
th
dave
Jul 21 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi Dave,

Thanks for posting in the community.

Currently I am looking for somebody who could help you on it. We will reply
here with more information as soon as possible.
If you have any more concerns on it, please feel free to post here.
Thanks!

Best regards,

Gary Chang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

Jul 21 '05 #2

P: n/a
Hi Dave,

Thanks for posting in the community.

First of all, I would like to confirm my understanding of your issue.
From your description, I understand that you wants to know is the webpart
in the link below will work on both WSS site( windows sharepoint services)
and SPS site(SharePoint Portal Server).
Have I fully understood you? If there is anything I misunderstood, please
feel free to let me know.

I think the link you specify as below
http://www.devx.com/dotnet/Article/17518/0/page/2
will work on both SPS and WSS site.
Usually a Webpart for 2003 will work on both WSS and SPS site, except the
webpart using some Object Modal which is specified to WSS site or SPS site.

For detailed information about OM of SPS 2003 , you may refer to the links
below.
SharePoint Products and Technologies
http://msdn.microsoft.com/library/de...us/spptsdk/htm
l/SPPTOverview.asp

SharePoint Products and Technologies 2003 Software Development Kit (SDK)
http://www.microsoft.com/downloads/d...fe5-daee-4d10-
980f-789b827967b0&displaylang=en

For more information about Webpart development, please take a look at the
link below.

A Developer's Introduction to Web Parts
http://msdn.microsoft.com/library/de...us/odc_sp2003_
ta/html/sharepoint_northwindwebparts.asp

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Jul 21 '05 #3

P: n/a
The only thing that would make your web part work on SPS an d not WSS would
be using the classes from Microsoft.Sharepoint.Portal namespace and its
subnamespaces ...
I don"t think there is something that can work on WSS and not on SPS (SPS is
a higher layer on top of WSS...) and if you have SPS on the machine, then
you also have WSS, which probably would make your code alright ...
"dave" <dy@onlinelg.com> wrote in message
news:1E**********************************@microsof t.com...
if i created a web part in vs.net like http://www.devx.com/dotnet/Article/17518/0/page/2 is it possible to use the
web part in both the sharepoint services environment and the sharepoint
portal environment without modification?
new to these products and not sure where to look for resources
thx
dave

Jul 21 '05 #4

P: n/a
Hi Dave,

I appologize for my confusion, in common sense, I agree with Malek's
suggestion. Usually a webpart works on WSS will work on SPS too. Since SPS
will has some features that WSS did not have, so if you use the feature in
your webpart on WSS, the webpart will not work properly.

But there also will be unexpected exception, we need to analyze the
concrete problem when we encounter the exception.

Thanks for you understanding.

If you have more concern on this issue, please feel free to post here.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

Jul 21 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.