New answers tagged

3

I believe there is no error in creating Web Application. Based on this approach I am trying to help. You need to create any Site Collection into it, Web Application cannot be opened directly. You can create a root level Site Collection. As you are new to SharePoint 2013 you can go through Create a Web Application and Site Collection in SharePoint 2013 Let ...


2

No, it may not be a requirement that an existing web application has a host header before you create a new web application that does, however it depends on the configuration. Using SSL, depending upon the certificate and IIS configuration (specifically whether you use SNI, Server Name Indication), you may need to bind each web application to a separate IP ...


0

It is a usual behavior of SharePoint... When you deploy SharePoint package , it will place the files & it's related DLLs to their appropriate location.. It is necessary to reset is to connect those file with each other to get a reference from different locations ... This is the simple definition from my end to understand why it's necessary to reset the ...


2

Actually, there's no such thing as "deploying a Web part to a site collection". You deploy a Web part with a WSP package; WSP packages (at least ones that contain Web parts) are deployed against specific Web applications. After that the feature containing the Web part is activated per site collection, but "activating a feature" is only a SharePoint logic ...


0

I don't think it is SharePoint Design issue, It is more IIS issue. When you deploy a solution, it deploys the DLL in GAC folder. IIS can't read those Dll until iisreset performed.Basically, IISreset does two things clear the memory reload all the DLLs from the GAC folder. One thing you can do, During your code you can't set Reset Web Server property to ...



Top 50 recent answers are included