Howto publish an ASP.NET website to MOSS 2007? - Sharepoint

This is a discussion on Howto publish an ASP.NET website to MOSS 2007? - Sharepoint ; Hello, being a newbie to C#/ ASP.NET/ MOSS 2007 I'm struggling with publishing either a Web Project or Website (both ASP.NET 2.0) to our company intranet on MOSS 2007. 1) The Web Project is created with VS 2005 (TFS), uses ...

+ Reply to Thread
Results 1 to 4 of 4

Howto publish an ASP.NET website to MOSS 2007?

  1. Default Howto publish an ASP.NET website to MOSS 2007?

    Hello,

    being a newbie to C#/ ASP.NET/ MOSS 2007 I'm struggling with publishing
    either a Web Project or Website (both ASP.NET 2.0) to our company intranet on
    MOSS 2007.

    1) The Web Project is created with VS 2005 (TFS), uses aspx-webforms,
    ascx-webusercontrols and webparts. It actually works as "standalone" website,
    which is tested locally on ASP.NET Local Development Server (Vista Business)
    and doesn't make use of any specific MOSS 2007 features like lists or
    document libraries.

    Nevertheless, it has to be a "full featured" part of our company intranet on
    MOSS 2007 (e.g. best like a personal website in "mysite" with own tab on top
    and SharePoint-layout).

    2) Having neither "physical" access to MOSS (via RDP) nor to the Central
    Administration Website I created a testing website called "VSWeb" via browser
    beneath my personal website ("http://mysite/hp/VSWeb/"). I'm able to connect
    to the testweb with SharePoint Designer happily moving files between my
    workstation and the testweb, but unfortunately codebehind-files are ignored,
    the testweb doesn't have a bin-folder and dll-files are blocked anyway (ok,
    security reasons..).

    As mentioned above I have also tried with a simple website in VS 2005
    (Default.aspx + WebUserControl.ascx), another VS project with a Web User
    Control and a C# "wrapper"-class functioning as a webpart. Assemblies are
    always signed and strong named. But as said I do not have access to the MOSS
    GAC...

    Is there anything I overlooked?

    Thanks for any answers!
    --
    Hans Peter

  2. Default RE: Howto publish an ASP.NET website to MOSS 2007?

    You cannot directly deploy a full-fledge ASP.NET appliation on to MOSS 2007
    and make it run under MOSS 2007. As far as know, there is no guidance from
    Microsoft
    for this.
    Sometime back i've ****yzed and came up with following options
    1. Use page viewer webpart to render ASP.NET pages
    2. Develop ASP.NET PAges as user controls, create custom web parts in MOSS
    2007 and load the user controls on the fly (programmatically)
    3. Deploy ASP.NET appllication as layouts application under _layouts folder
    4. Use smartparts to render ASP.NET user controls

    The following blog post has more details on various options
    http://blogs.msdn.com/cjohnson/archi...mp-wss-v3.aspx

    After all the experiements i'e decided there is no clear guidance anywhere
    to support deploying custom ASP.NET application on MOSS 2007

    --
    ----
    Sundar Narasiman,
    http://dotnetbuzz.spaces.live.com/



    "HP" wrote:

    > Hello,
    >
    > being a newbie to C#/ ASP.NET/ MOSS 2007 I'm struggling with publishing
    > either a Web Project or Website (both ASP.NET 2.0) to our company intranet on
    > MOSS 2007.
    >
    > 1) The Web Project is created with VS 2005 (TFS), uses aspx-webforms,
    > ascx-webusercontrols and webparts. It actually works as "standalone" website,
    > which is tested locally on ASP.NET Local Development Server (Vista Business)
    > and doesn't make use of any specific MOSS 2007 features like lists or
    > document libraries.
    >
    > Nevertheless, it has to be a "full featured" part of our company intranet on
    > MOSS 2007 (e.g. best like a personal website in "mysite" with own tab on top
    > and SharePoint-layout).
    >
    > 2) Having neither "physical" access to MOSS (via RDP) nor to the Central
    > Administration Website I created a testing website called "VSWeb" via browser
    > beneath my personal website ("http://mysite/hp/VSWeb/"). I'm able to connect
    > to the testweb with SharePoint Designer happily moving files between my
    > workstation and the testweb, but unfortunately codebehind-files are ignored,
    > the testweb doesn't have a bin-folder and dll-files are blocked anyway (ok,
    > security reasons..).
    >
    > As mentioned above I have also tried with a simple website in VS 2005
    > (Default.aspx + WebUserControl.ascx), another VS project with a Web User
    > Control and a C# "wrapper"-class functioning as a webpart. Assemblies are
    > always signed and strong named. But as said I do not have access to the MOSS
    > GAC...
    >
    > Is there anything I overlooked?
    >
    > Thanks for any answers!
    > --
    > Hans Peter


  3. Default Re: Howto publish an ASP.NET website to MOSS 2007?

    On Nov 22, 11:50 am, Sundar Narasiman
    <SundarNarasi...@discussions.microsoft.com> wrote:
    > You cannot directly deploy a full-fledge ASP.NET appliation on to MOSS 2007
    > and make it run under MOSS 2007. As far as know, there is no guidance from
    > Microsoft
    > for this.
    > Sometime back i've ****yzed and came up with following options
    > 1. Use page viewer webpart to render ASP.NET pages
    > 2. Develop ASP.NET PAges as user controls, create custom web parts in MOSS
    > 2007 and load the user controls on the fly (programmatically)
    > 3. Deploy ASP.NET appllication as layouts application under _layouts folder
    > 4. Use smartparts to render ASP.NET user controls
    >
    > The following blog post has more details on various optionshttp://blogs.msdn.com/cjohnson/archive/2006/09/05/application-develop...
    >
    > After all the experiements i'e decided there is no clear guidance anywhere
    > to support deploying custom ASP.NET application on MOSS 2007
    >
    > --
    > ----
    > Sundar Narasiman,http://dotnetbuzz.spaces.live.com/
    >
    > "HP" wrote:
    > > Hello,

    >
    > > being a newbie to C#/ ASP.NET/ MOSS 2007 I'm struggling with publishing
    > > either a Web Project or Website (both ASP.NET 2.0) to our company intranet on
    > > MOSS 2007.

    >
    > > 1) The Web Project is created with VS 2005 (TFS), uses aspx-webforms,
    > > ascx-webusercontrols and webparts. It actually works as "standalone" website,
    > > which is tested locally on ASP.NET Local Development Server (Vista Business)
    > > and doesn't make use of any specific MOSS 2007 features like lists or
    > > document libraries.

    >
    > > Nevertheless, it has to be a "full featured" part of our company intranet on
    > > MOSS 2007 (e.g. best like a personal website in "mysite" with own tab on top
    > > and SharePoint-layout).

    >
    > > 2) Having neither "physical" access to MOSS (via RDP) nor to the Central
    > > Administration Website I created a testing website called "VSWeb" via browser
    > > beneath my personal website ("http://mysite/hp/VSWeb/"). I'm able to connect
    > > to the testweb with SharePoint Designer happily moving files between my
    > > workstation and the testweb, but unfortunately codebehind-files are ignored,
    > > the testweb doesn't have a bin-folder and dll-files are blocked anyway (ok,
    > > security reasons..).

    >
    > > As mentioned above I have also tried with a simple website in VS 2005
    > > (Default.aspx + WebUserControl.ascx), another VS project with a Web User
    > > Control and a C# "wrapper"-class functioning as a webpart. Assemblies are
    > > always signed and strong named. But as said I do not have access to the MOSS
    > > GAC...

    >
    > > Is there anything I overlooked?

    >
    > > Thanks for any answers!
    > > --
    > > Hans Peter


    Actually, you can, but it's a pain.

    1: Use complete namespaces
    2: Fully sign everything in the site.
    3: Drop the compiled DLL into the server's GAC. (Usually C:\Windows
    \Assembly or C:\WINNT\Assembly -- It depends on your upgrade path to
    the current server)
    4: Edit the sharepoint web.config to add the dll as a safe control
    5: publish the aspx pages to the sharepoint server.
    6: Edit the aspx pages to have a reference directive to the DLL
    7: Recycle the AppPool.

    I'd suggest trying this on a Dev Server or a Backup before doing it on
    Production.

  4. Default RE: Howto publish an ASP.NET website to MOSS 2007?

    Hello Sundar,

    thanks for your appreciated answer. I've started to play around with what I
    thought was the easiest point ("_layouts"): I verified the existence via
    browser in my own personal website, e. g.
    http://mysite/personal/hp/_layouts/ManageFeatures.aspx, but I couldn't find
    the _layouts-folder when connecting to http://mysite/personal/hp/ with
    SharePoint Designer.

    My constraints:

    - little developer experience
    - developer machine lacks w2k3 server with wss3 and/or MOSS 2007
    - developer machine lacks wss sdk etc.
    - no admin privileges on productive MOSS 2007 (not to bad, I think, being
    unliable for any damage;-)

    I would be more than happy if I could deploy any example on MOSS 2007 -
    preferably via SharePoint Designer - that makes use of a simple web user
    controls or webparts, but I always get stuck on three points:
    1) Copying a project dll to some "bin" folder does not work - besides there
    is none in http://mysite/personal/hp/...
    2) Getting a productive "hold" of my ascx-file, I copied into
    http://mysite/personal/hp/ (ok - it's not a webpart, but how can I "grab"
    it?)...
    3) A big gap in explaining the deployment process to MOSS 2007 in excellent
    examples like
    http://office.microsoft.com/home/vid...HA102199841033

    I'm fascinated in seeing VS 2005 and SharePoint Designer interact perfectly
    in the video, but the comment "simply use 'add file'" doesn't give me an
    explanation of how the example webpart (outputting "<span>Hello!</span>"
    only) will wander from my machine to the server.

    Is there any way at all deploying web applications via SharePoint Developer
    in a restricted environment (see constraints)?

    Best regards!
    --
    Hans Peter


    "Sundar Narasiman" wrote:

    > You cannot directly deploy a full-fledge ASP.NET appliation on to MOSS 2007
    > and make it run under MOSS 2007. As far as know, there is no guidance from
    > Microsoft
    > for this.
    > Sometime back i've ****yzed and came up with following options
    > 1. Use page viewer webpart to render ASP.NET pages
    > 2. Develop ASP.NET PAges as user controls, create custom web parts in MOSS
    > 2007 and load the user controls on the fly (programmatically)
    > 3. Deploy ASP.NET appllication as layouts application under _layouts folder
    > 4. Use smartparts to render ASP.NET user controls
    >
    > The following blog post has more details on various options
    > http://blogs.msdn.com/cjohnson/archi...mp-wss-v3.aspx
    >
    > After all the experiements i'e decided there is no clear guidance anywhere
    > to support deploying custom ASP.NET application on MOSS 2007
    >
    > --
    > ----
    > Sundar Narasiman,
    > http://dotnetbuzz.spaces.live.com/


+ Reply to Thread

Similar Threads

  1. Disallow users to publish in MOSS 2007
    By Application Development in forum Sharepoint
    Replies: 1
    Last Post: 09-07-2007, 11:53 AM
  2. Replies: 1
    Last Post: 06-27-2007, 10:51 PM
  3. SharePoint Desiger sought to help with branding MOSS 2007 website
    By Application Development in forum Sharepoint
    Replies: 0
    Last Post: 12-15-2006, 03:25 PM
  4. Re: Cannot save (publish) my Excel 2007 spreadsheet to Sharepoint 2007
    By Application Development in forum Sharepoint
    Replies: 0
    Last Post: 12-04-2006, 01:45 AM
  5. Publish website
    By Application Development in forum Inetserver
    Replies: 14
    Last Post: 09-24-2004, 10:28 AM