Deploying web applications to a file share

  • Deploying web applications to a file share Emad

    what do you think about deploying the SharePoint IIS web sites to a Shared file location (\\Fileserver\WWWRoot\Application1 for example) in contrast with deploying a copy locally to each Web Front End server (c:\inetpub\wwwroot\application1 for example).

    Deploying locally to WFEs can usually take time to copy physical files to the different WFEs and we make efforts in making them synched and sometimes we have problems because the two servers are not exactly the same and so on.

    Are there any problems with the approach of deploying a Sharepoint IIS web site on a shared location path?

  • OMG Noooooooooooooooooooooooooooooooooooooooooooooooooooooooo!

    Sorry to be over dramatic, but you will end up in a world of pain if you even attempt to do this. Use SharePoint WSP solutions to deploy to multiple WFEs. This process is well documented and very simple, especially if you use the excellent wspbuilder at CodePlex.

    If you want some guidelines on SharePoint Development then pick up the free Muhimbi SharePoint Development Guidelines.

Related questions and answers
  • We are currently doing a POC for a client to use SharePoint 2010 for Records Managment. The client has around 200 content types, and a deep nested file plan of around 500 potential nodes. In order to route documents a peice of metadata called 'File Plan' has been created as a Managed Metadata field which corresponds to the eventual location within the Records Centre folder structure. We will set... Organizer you have to assign rules that depend on a specific content type. So in our case we have to create identical rules for different Content Types, for example if Content Type = Contract and File Plan

  • User Steven has the Active Directory account however his profile is not yet populated into SSP User profiles. NT Authenticated users have the access permission on "Shared Documents - Document Library". So, will Steven be able to access the "Shared Documents"? I guess, IIS will authenticate the user Steven to access the "Shared Documents" and SharePoint will authorize the user to View the items in "Shared Documents", is that right?

  • ;WebPartZone> and putting my webpart in there Adding .webpart-code directly into <AllUsersWebPart> where I define the page layout, in elements.xml Put the web part on the page layouts programmatic when creating site structure (deployment script) Add a hook that hooks in and adds the web part Problems with the solutions: The web part seems to become static, and can not be removed after it's created. would have to put .webpart-code in both a .webpart-file as well as in elements.xml (I want it to be stand alone as well as set by default). And making a mess in my elements.xml. Web

  • Using host file Loïc Wolff

    I created an application in SharePoint, lets call it and a site collection with the "Empty Site" template. Since I'm using it locally in a virtual machine in host-only mode, I had to edit my host file to add Now, whenever I access this website, I cannot click on "Site Action". All it does is add a # at the end of the URL. Since I'm in a host-only VM, i cannot change the DNS to make it work (that's the way we fixed it for a dev server).

  • I'm using VS 2010 to create a SP 2010 web part. I want to include my images, css files and js files in the VS project, and have them be deployed to the correct location. My understanding is that I should be using SPWebPartManager.GetClassResourcePath() to get the urls for these items, and that the files should end up in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\wpresources\{web part name}\{version}__{pk token}. Is the above correct, or is there a better way? How to I include these fines in the VS project so that they are deployed to this location - e.g.

  • I've created a Custom List ('Tooltips') in SharePoint. After this I used SPSource to reverse engineer the list into a feature. After installing and activating this feature, I want to add this list in a WebPart zone. When doing this, I get an error message : Tooltips: List View Web Part could not be added, list may be hidden. What's wrong with the list? feature.xml <?xml version="1.0... in InfoPath and FormWrapper." Version="" Hidden="FALSE" Scope="Web" DefaultResourceFile="core" ReceiverAssembly="MyApp.WebServices, Version=

  • within a user control and the XAP file deployed to _layouts. I'm testing the user control in both a web part and an application page. Both result in the same error reported by Internet Explorer.... The system cannot find the file specified. at MyNamespace.Page.InitializeComponent() at MyNamespace.Page..ctor() at MyNamespace.App.Application_Startup(Object sender, StartupEventArgs e... necessary. Any ideas on what might be causing this? Update: I've tried deploying the XAP file to a document library within the site and it works perfectly. This makes me wonder if there is some sort

  • into it. Either way, it then opens the file in Excel. The code to open the file is some client-side script that figures out the location of the Excel file in SharePoint, sets an href variable to that URL...Scenario: We have an internal application that ties Excel spreadsheets stored in a SharePoint doc lib with specific Opportunities in CRM. The user clicks on a button in the Opportunity and a Web... is causing this behavior? I can change the code to avoid it if I can figure out why it is happening. Is there any way through the SharePoint UI or APIs to "release" the document so that the original

  • Excel Web Services Error Paul Akerlind

    I have uploaded an xlsx file that I would like to use EWA to display using Excel Web Services. I have confirmed that the site is a trusted location and Excel Web Services is configured correctly from Central Admin. A simple spreadsheet works fine and renders in browser. However, for one particular worksheet I get an error when I try to point the EWA web part to it. It is indicating that it contains the following features that are unsupported by Excel Services. The error references sharepoint lists as the feature not supported. What is SharePoint Lists referring to? I removed the data

Data information