I implemented one web application in ASP.NET but when i am merging that inside the DNN it is giving the problem.
How can we assign the asp.net web application inside Dot Net Nuke.

What are the problems that you are having?

I suspect that this is going to be very difficult. Does the other application have to be "inside" of the DotNetNuke site?

I have seen asp.net applications installed in a subdirectory of the DotNetNuke site. When that is done, you have to refer to the asp.net app as mysite.com/myapp/page.aspx, etc.

You will also need to create a custom web.config for the asp.net app that is placed in the subdirectory. You will likely need to remove a lot of DotNetNuke's namespace, modules, handlers, etc. to get the app to work.

Dear Joseph Craig,

I have created one web application in visual studio, it is working fine in visual studio with PWS.

Then i am merging the same website inside the DNN.

When i run the application from the IIS it is giving the following problem..
-------------------------------------------------------------------------------
Server Error in '/DNN/sampleapplication' Application.

Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an object.]
DotNetNuke.Common.Globals.get_Status() +104
DotNetNuke.HttpModules.RewriterUtils.OmitFromRewriteProcessing(String localPath) +66
DotNetNuke.HttpModules.RequestFilter.RequestFilterModule.FilterRequest(Object sender, EventArgs e) +202
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +79
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +170

Does this error come from your DotNetNuke portal, or from your application?

If it is coming from your application, then it seems that DotNetNuke is interfering with your application. That's where you need to start removing DotNetNuke stuff in your application's web.config file.

I did some additionial reading and saw one comment that the "right" way to do this is by installing your application in a "Virtual Directory" that is mapped inside of your DotNetNuke application, but not physically in it. I know very little about this, but here is a reference: http://www.iis.net/learn/get-starte...ies-on-iis

This seems like a better way to go, and also seems designed for what you are trying to do.

Steps i followed:
---------------------------------
1. Created application in Visual Studio
2. Tested the application. It is working fine.
3. Copy and pasted the asp.net application folder inside the DotNetNuke.
4. Made that folder as web application inside DotNetNuke.
5. Browsing the application from IIS.

My application is working fine in Visual Studio . But when i am running the same website from the IIS it is giving the above problem.

Rather than placing the application in a directory inside of your DotNetNuke site, try the recommendation to install it as a "Virtual Directory" and map it to your DotNetNuke site.

Okay i have integrated the same application in IIS. It is working fine as a separate application through the IIS.

Can i know how to map that application to the DotnetNuke.