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.

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.

Try the msd2d.com forum at www.msd2d.com/wb/default.asp?action=10&fid=56

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.

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.

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.

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?