Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Add a custom webapp to Sharepoint

  Asked By: Shonda    Date: Nov 25    Category: Sharepoint    Views: 1295

We have created a webapp that is referencing a third party app Dundas
Map for .net. When we install it on a basic webpage in IIS it works
fine, but when we try to bring it into sharepoint it isn't working. It
pulls the data from the SQL data base and compiles it, but won't bring
up the map at all. Dundas says it should work. Any suggestions as to
where we are going wrong?

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Candy Walter     Answered On: Nov 25

When you say you install  it on a basic  web page and it works. Have you tried
usinbg a Page Viewer web part and view it through the basic web page?

 
Answer #2    Answered By: Leanne Rios     Answered On: Nov 25

when we have it on our webserver without sharepoint  - it works just fine. How
would we do it as a page viewer web part?

 
Answer #3    Answered By: Zachary Roberts     Answered On: Nov 25

Put it in an unmanaged path. Create a virtual directory under the defult web
site in IIS and put your web page there, and then on the central admin site go
to http://[server:portnumeber/_admin/scprefix.aspx and exclude the path to the
virtual directory where your web page lives.

 
Answer #4    Answered By: Maura Durham     Answered On: Nov 25

In Windows SharePoint Services 3.0 it should be in _Layouts. I believe
that is the best practice. I am sure one of the devs can tell you more.

 
Answer #5    Answered By: Jagat Pandit     Answered On: Nov 25

Putting your application under _layouts is not necessary. I prefer to
put this type of web application in its own IIS web site if possible.
Otherwise, I place it under the Windows SharePoint Services web
application that consumes the content.

In IIS Manager, make sure that the virtual directory is an "ASP.Net
application" (the Virtual Directory tab in properties should have a
non-blank application name). Once that is done, perform an IISRESET.

Excluded managed paths are not necessary in v3, only in v2

 
Answer #6    Answered By: Jerod Carrillo     Answered On: Nov 25

I meant to say in the layouts *if* you want it in the same URL. I would
not create a virtual directory in the same IIS Virtual Server.

 
Answer #7    Answered By: Hema Pasupuleti     Answered On: Nov 25

Since ASP.NET is in charge in a WSS v3 Web Application, ANY IIS Virtual
Directory that is identified as an ASP.NET application (has application
state) will be treated in the same way that _layouts is. So, many people
put the custom  application under the WSS site but under a custom Virtual
Directory (much like a v2 excluded Managed Path but in v3 the exclusion
is always implied because ASP.NET is handling traffic to the website).
The custom application can have full access to the SharePoint Web
Application if the programmer desires.

 
Answer #8    Answered By: Candis Kinney     Answered On: Nov 25

You can 'just' put the application in a
subdirectory of your sharepoint webapp  and 'it just should work'
without any sharepoint  configuration, but but there are two catches...

1. the application must be ASP.NET 2.0 (and not 1.1 for example). (the
application pool can handle only one .NET engine).

2. Your ASP.NET application inherits settings from any web.config file
of the parents, thus SharePoint's web.config, including disabling
modules, handlers ect that your application may need.

I believe there are some blog posts about this subject where handlers
and modules have to be 'reinstated' in the web.config of the child
ASP.NET application.

(the most basic  settings of an ASP.NET application ultimately come from
the machine.config.)

 
Didn't find what you were looking for? Find more on Add a custom webapp to Sharepoint Or get search suggestion and latest updates.




Tagged: