Posted By: Charles | May 11th, 2006 @ 11:22 AM | 57,427 Views | 25 Comments
Windows SharePoint Services 3.0 builds upon the Web Part infrastructure that was introduced in ASP.NET 2.0. This tutorial demonstrates how to create an ASP.NET Web Part 2.0 project from scratch and to get it up and running within a Windows SharePoint Services 3.0 site.
Media Downloads:
Rating:
0
0

Very nice... 

I have one question about adding web parts as safe to the web.config file...

We are using Sharepoint Portal server and I don't have a web.config located in the inpub/wwwroot directory as shown in the clip.

Where is the web.config file we need to edit for Portal Server?
Thank you in advance.

Mad

doncho
doncho
Evangelist
Are you using SPS 2003 or Office SharePoint Server 2007 beta 2?
Doncho, thanks I am using Office SharePoint Server 2007 beta 2

Doncho...

I am still needing the answer - you or anyone at MS care to answer?  Time is of the essense...
Expressionless

Never mind Doncho - found it...

In our case

C:\Inetpub\wwwroot\wss\VirtualDirectories\c2170bb3-43df-46d7-9737-303d33ba0d0a

One of the virtual directories...

Works great!

Big Smile:D

doncho
doncho
Evangelist

Sorry I took so long to get back to you.  Glad you found it.

 

Good demo. I have some questions about making it work for me on my system. I am running WSS 3.0 Beta 2 and the bin directory and web.config file were not located at C:\inetpub\wwwroot\. I did find the virtual directories that someone else pointed out but again no folder specifically name "bin" was there. Could the litware.dll be placed under the _app_bin directory or the App_GlobalResources directory? I modified the web config file there and created a bin folder. When I go to the Web Part Gallery and select New, I do not see the litware web part to add.

Perplexed

Any suggestions?

Sounds like you have done the same as I did...  Not sure why it wouldn't show up...

AH HA! I think I got it figured out. I had to name the class in the web.config file rather than use "*". Then SharePoint sees the webpart. Funny though, I can go back to the web.config file and change the Typename back to "*" and it still works.

Big Smile
Microsoft Communities