Confused Newbie: VS 2005 Project Type for ASP.NET 2.0 Web Parts; also How to Deploy?

Hello,

I've recently started getting into Web Parts, and have managed to develop a
couple that run OK on the ASP development server that comes with VS 2005.
The problem is that I can't figure out how I'm supposed to deploy them to an
actual SPS server. I'm not even sure if I'm using the correct project type
in VS to develop my Web Parts (I'm using the ASP.NET Web Site template, and
the ASP.NET 2.0 Web Parts in the toolbox).

All the deployment information I've managed to find seems targeted toward VS
2003 and the Web Part Templates that are available for that version (is an
updated version of those templates available for VS2005?), and I can't seem
to adjust those instructions to work with my projects.

So could someone give me the rundown on what this process should look like,
including proper project type, compilation options, deployment procedure and
"other" file I need to add by hand (i.e., manifests)?

Also, are ASP.NET 2.0 Web Parts compatible with the current version of
SharePoint (2.0), or do I have to use SharePoint 3.0 beta?

Helpful suggestions, information and links all greatly appreciated!

Keith

Ken
Wed May 17 12:15:48 CDT 2006

Web Parts developed in VS2005 (.NET 2.0) are not compatible with SPS 2003 or
(with one exception) WSS 2.0. Those Web Parts will need SPS 2007 or WSS 3.0
(I assume that's the version). I forget the name of it but there is a 3rd
party product that will let you use the new Web Parts in WSS 2.0 but even
that will not work with SPS 2003.

Hope that helps,

Ken
"Keith" <keith@alh.com> wrote in message
news:OAEX1HdeGHA.3808@TK2MSFTNGP02.phx.gbl...
> Hello,
>
> I've recently started getting into Web Parts, and have managed to develop
> a couple that run OK on the ASP development server that comes with VS
> 2005. The problem is that I can't figure out how I'm supposed to deploy
> them to an actual SPS server. I'm not even sure if I'm using the correct
> project type in VS to develop my Web Parts (I'm using the ASP.NET Web Site
> template, and the ASP.NET 2.0 Web Parts in the toolbox).
>
> All the deployment information I've managed to find seems targeted toward
> VS 2003 and the Web Part Templates that are available for that version (is
> an updated version of those templates available for VS2005?), and I can't
> seem to adjust those instructions to work with my projects.
>
> So could someone give me the rundown on what this process should look
> like, including proper project type, compilation options, deployment
> procedure and "other" file I need to add by hand (i.e., manifests)?
>
> Also, are ASP.NET 2.0 Web Parts compatible with the current version of
> SharePoint (2.0), or do I have to use SharePoint 3.0 beta?
>
> Helpful suggestions, information and links all greatly appreciated!
>
> Keith
>

Keith
Wed May 17 15:14:02 CDT 2006


"Ken Ingram" <ken.ingram@stratech.com> wrote in message
news:8TIag.472$Qg.327@tornado.southeast.rr.com...
> Web Parts developed in VS2005 (.NET 2.0) are not compatible with SPS 2003
> or (with one exception) WSS 2.0. Those Web Parts will need SPS 2007 or WSS
> 3.0 (I assume that's the version). I forget the name of it but there is a
> 3rd party product that will let you use the new Web Parts in WSS 2.0 but
> even that will not work with SPS 2003.

Well, that clears up that.

Regardless, my questions still stand regarding ASP.NET 2.0 Web Parts and
deploying them to SharePoint 3.0/2007. What's the approach/project
type/etc.? Is there any documentation or samples on this? Tutorials maybe?

jholliday
Wed May 17 17:10:50 CDT 2006

Not sure regarding 3.0/2007 however, the Son of SmartPart Web Part by
Jan Tielens will allow you to run ASP.NET 2.0 UserControls and WebParts
in the current version of SharePoint. Just an FYI.

http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=6cfaabc8-db4d-41c3-8a88-3f974a7d0abe

Jeff

Gary
Thu May 18 05:59:24 CDT 2006

I would wait a couple of weeks to see if this information is released
with/soon after Beta2 of Office 2007. Right now there is no information on
it.

--
Gary A. Bushey
SPS MVP
bushey@mindspring.com


"Keith" <keith@alh.com> wrote in message
news:ejryv8eeGHA.2068@TK2MSFTNGP02.phx.gbl...
>
> "Ken Ingram" <ken.ingram@stratech.com> wrote in message
> news:8TIag.472$Qg.327@tornado.southeast.rr.com...
>> Web Parts developed in VS2005 (.NET 2.0) are not compatible with SPS 2003
>> or (with one exception) WSS 2.0. Those Web Parts will need SPS 2007 or
>> WSS 3.0 (I assume that's the version). I forget the name of it but there
>> is a 3rd party product that will let you use the new Web Parts in WSS 2.0
>> but even that will not work with SPS 2003.
>
> Well, that clears up that.
>
> Regardless, my questions still stand regarding ASP.NET 2.0 Web Parts and
> deploying them to SharePoint 3.0/2007. What's the approach/project
> type/etc.? Is there any documentation or samples on this? Tutorials
> maybe?
>
>

JohnnyBoyWonder
Mon Jun 12 05:48:02 CDT 2006

Does anyone know if this documentation is out yet?

"Gary A. Bushey" wrote:

> I would wait a couple of weeks to see if this information is released
> with/soon after Beta2 of Office 2007. Right now there is no information on
> it.
>
> --
> Gary A. Bushey
> SPS MVP
> bushey@mindspring.com
>
>
> "Keith" <keith@alh.com> wrote in message
> news:ejryv8eeGHA.2068@TK2MSFTNGP02.phx.gbl...
> >
> > "Ken Ingram" <ken.ingram@stratech.com> wrote in message
> > news:8TIag.472$Qg.327@tornado.southeast.rr.com...
> >> Web Parts developed in VS2005 (.NET 2.0) are not compatible with SPS 2003
> >> or (with one exception) WSS 2.0. Those Web Parts will need SPS 2007 or
> >> WSS 3.0 (I assume that's the version). I forget the name of it but there
> >> is a 3rd party product that will let you use the new Web Parts in WSS 2.0
> >> but even that will not work with SPS 2003.
> >
> > Well, that clears up that.
> >
> > Regardless, my questions still stand regarding ASP.NET 2.0 Web Parts and
> > deploying them to SharePoint 3.0/2007. What's the approach/project
> > type/etc.? Is there any documentation or samples on this? Tutorials
> > maybe?
> >
> >
>
>
>