Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

SharePoint and embedded ASPX

  Asked By: Jamie    Date: Nov 16    Category: Sharepoint    Views: 3157

I have something interesting to discuss with u all and take
ur suggestions. I have a .net application (aspx pages) which I am
trying to embed inside a SharePoint webpart (Page Viewer Webpart).
That means I am trying to integrate two different and discrete
worlds - One side is SharePoint and another side is .NET Application.

The reason behind this is to take complete advantage of the
features of the two different technologies. Now, my question is,
whether it is possible for the two technology to talk to each other?
In the sense, I want to display the .NET pages inside the embedded
SharePoint webpart based on the access rights of the SharePoint site
users. And also I want to pass the SharePoint users id (name) to the
embedded asp.net page. Is this possible and if so then how?

Let me be more clear. I have a complete .NET application
which starts with login page. Now I am embedding the application
inside the "Page Viewer Web Part". So, since I am already logging in
the SharePoint site with the necessary userid and password
(SharePoint user's id), I want the same username to be passed across
to the embedded .NET page (inside the Page viewer webpart) so that I
can skip the .NET's login page and show the next page which has a
column that displays the logged in username. That means, I have to
pass the login id of the SharePoint user to the embedded .NET page
and display it there. Is this possible because both are in different
worlds and if yes, then how? Kindly reply with adequate information,
articles, code (even better).

Share: 

 

7 Answers Found

 
Answer #1    Answered By: Gopal Jamakhandi     Answered On: Nov 16

The QueryString is probably your best bet. Failing that, perhaps a
hidden SharePoint list could hold the value saved from the SharePoint
page and retrieved on the .NET application  page.

 
Answer #2    Answered By: Kristina Cox     Answered On: Nov 16

This is a very high interest of mine too. I believe the Sharepoint model (WSS and SPS) is Best-of-Bread for “Portal/Intranet Management” especially when you consider its integration with Outlook and Office in particular (why fight it) but I would like to leverage applications and web  controls and web parts I’ve developed using ASP.NET 1.1 and 2.0.

It is my understanding that when we move to MOSS 2007 we will have both MS CMS (a more directly compatible ASP.NET 2.0 application  environment) and Sharepoint Portal Services capabilities in one product with one Sharepoint Designer or a full version of Visual Studio as an IDE.

Not sure how this works in the mean time…but use of CEWP, PVWP and development of Web Services are the three options I’ve been working with.

This group seems primarily devoted to learning and understanding install, configuration and what you can do out-of-the-box with out a lot of custom coding beyond the Sharepoint managed web part  types available ….

I hope the rest of the group responds or directs us to a more “Customizable” discussion group for these kinds of questions.

 
Answer #3    Answered By: Delbert Frederick     Answered On: Nov 16
 
Answer #4    Answered By: Kalyan Pujari     Answered On: Nov 16

I understood that you want to implement asp.net application  inside the sharepoint.
One more thing both are not different technologies  but the same technology. sharepoint  is totally an asp.net application itself.

Open the IIS, Create a virtual folder under the sharepoint hosted website. and copy all the contents of your .net application in this folder.
and Go to sharepoint Portal Central administration,
Under Portal site  and Virtual Server Configuration,
Click on Portal Site and Virtual Server Configuration,
Click on your virtual site(http://wsjog-server11:81/),
Now Under Virtual Server Management, click on Define Managed Paths,
In the New Path, Add your virtual folder name you have created and select the Type as "Excluded Path"
Now Click OK.

Your ASP.net application is hosted inside  SPS 2003.
Now give this link in the page  viewer webpart, it will not ask username  and password again.

 
Answer #5    Answered By: Allison Stewart     Answered On: Nov 16

Have you tried to use Smartparts? In this case, one would develop the application  as a ASP.NET user  control (.ascx), and deploy it to Sharepoint server with the .ascx file and the associated binary. Once this is done, the smart part  can be configured to "host" your ascx control, and provide more functionality than a CEWP. This way, you can even make the smart parts connectible to one another.

 
Answer #6    Answered By: Emmett Hyde     Answered On: Nov 16

I'm not a big SmartPart fan. The ASCX controls must be preloaded into an
excluded managed path on every Virtual Server before the Web Part
wrapper can be used.

It isn't difficult to roll your own Web Part wrapper to host an ASCX
controls that can be embedded  within the Web Part Package CAB and
deployed at the same time and scope as the Web Part using the
ClassResourcePath. IMHO, this is a much superior way of developing Web
Parts that consume User Controls.

 
Answer #7    Answered By: Michelle White     Answered On: Nov 16

So, if I am hearing you all correctly, it is probably more efficient and flexible to roll my own custom ascx controls in my custom Sharepoint web  parts. While Smart Parts is kind of a “Sharepoint Web part  like” approach to integration with ASP.NET apps, it has some install and setup overhead that may get difficult to wrap-up and deploy?

Besides, the Smart Parts approach seems to assume the ASP.NET application  data base is completely separate from the WSS or SPS Database... While this may be desirable (and advisable) in many cases, I would like to develop Web parts that can Query, combine and display  both data stored in Sharepoint lists/libraries AND ASP.Net application data in a separate database.

Questions:

I have a single SBS server with Sharepoint “Companyweb” migrated to a single “Production” MS SQL 2003 data base. Admin DB still on MSDE. Now I want to set up a “Development” Data Base for Sharepoint projects and separate ASP.Net application databases for both “Production” and “DEV”.

Has anyone gone through this process that can “hold my hand” on setting this up?

 
Didn't find what you were looking for? Find more on SharePoint and embedded ASPX Or get search suggestion and latest updates.




Tagged: