Click here to Skip to main content
15,846,038 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:

I have a c# ASP.NET application (6-8 pages) that my boss want to convert it into SharePoint webpart.

I found out that the Webpart deployment is very tricky. My question is:

Is it practical for us to convert our application to webpart, have anyone did it suceessfully? Please advise.


Herman<T>.Instance 18-Jul-11 10:32am    
ask your Boss what is his goal to have the site under sharepoint (intended for internal use) in stead of keeping it (internal and external use).

The other way is to use ascx files. Create in sharepoint a new page and attach the needed ascx- files to it.

1 solution

Just to clarify what a webpart is: a composite server side control. You can do some pretty complex stuff with that. But server side controls take a bit of knack to develop and have several gotchas so I'd be aware of calculating that risk in to your estimates.

What you can do to make life easier is have a webpart act as a page controller which posseses a panel taking most of the space. Then you can load ascx controls up inside the panel. This will make development of more complex "pages" less tedious as otherwise you would need to create them totally programatically.
Share this answer

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900