Sharepoint webpart as a developing tool ?

Question

1.00/5 (1 vote)

See more:

Hi;

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.

Thanks

Posted 18-Jul-11 4:29am

dondo1020

Add a Solution

Comments

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 asp.net (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

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Chris_Green · Answer 1 · 2011-07-18T05:29:00

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.