Currently I'm running several websites that have several (branded) duplicates each, in the same IIS.
I wanted to have an easy overview of all the website groups so I used a naming convention like [siteName].[brandCode].
But lo and behold, IIS has its very own (seemingly random) way of ordering the entries in the "Web Sites" folder.
Any suggestions
(and yes, I use different application pools, but that's not what I'm aiming for)
You'll need to edit the IIS Metabase to reorder those. I can't remember if theres a tool to do it in IIS6 but you can use MetaEdit for IIS7 so that might be backwards compatible.
If not, the metabase is just an XML file so you can hand edit it (take a backup first) in notepad.
as you are running IIS6, Install IIS6 Resource Toolkit and run Metabase Explorer, did the trick for me
I always click on the "Web Sites" folder in IIS Manager and sort the list in the right panel by description.
I think there is no other option.
Related
I want to display like an "under maintenance" page, while I restart (stop and then start) my IIS .net core website.
I want to do this, because I often need to replace some .dll's and I also want to tell the users, that the website is still active, just under construction for some minutes.
I need to stop the website, otherwise I'm not able to replace the .dll files.
Is there a good way to do this directly in IIS? Maybe also another nice way to do this, despite IIS?
You are maybe looking for app_offline.html
Placing this file into the root of the web app will cause stopping the app and serve that single file instead. I did use that with asp.net. First versions of asp.net core did not support it but meanwhile they should as the doc states.
https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.0#appofflinehtm
I've made my first website in ASP.NET MVC 4 for a customer, and he bought a host at 1eurohosting.net. On their website's FAQ it says
"Do you offer Windows based services?
We do not. We only offer Linux based services."
I've read that its still possible to run a MVC4 application on linux using mono, but how would I do this?
What I've tried so far is publish the website by right clicking solution explorer, and following the steps when u click "publish". The publishing works fine, and the files are on the webserver, but it doesn't run, because I think I need to use mono.
I don't know what to do at this point. What do I do next? If I have to use mono, how can I use it?
It seems that I either need a host that supports IIS or Mono. I dont think my current webhost supports Mono, I am still going to try and contact them, though.
I have successfully set up an API using ASP.NET MVC 4 on IIS6 (I used Phil's tutorial). When testing, we had it as the "Default website" and so there was no conflict with anything else. I am now being asked to set this up within a FOLDER of an existing website (the existing website is in ASP 1.0...and I cannot modify this...so I would some sort of virtual...something?). So basically, if we have https://www.ourcompany.com, they want the API to be available through https://www.ourcompany.com/api/.
Is this even possible? Phil's tutorial talks about setting up a Virtual Application, but I don't have that option in IIS (and if I had, I'm not knowledgeable enough about IIS to know if that would even allow me to access the API that way). I don't want anything that I set up to mess up the current website either, and there are a couple steps in the tutorial that I'll freely admit I don't fully understand.
If your curious as to WHY, the only advantage (besides being "neat") is so that the same SSL Cert can be used.
Yes that's definately possible at my work we had a similar setup, IIS6, a .NET 3.5 web, with a .NET 4.0 web nested underneath.
You would just set it up as a virtual directory underneath the parent website, point it to your folder, and ensure the value for the "Execute Permissions" dropdown is "Scripts Only" or above, and the correct .NET framework version selected on the ASP.NET tab.
There may be additional values you may need to over-write in your child web.config file, or, alternatively, wrap the entire parent web config with a "Location" attribute.
Forgot to mention, you may need to add manual script mappings for the child web if it doesn't work by default. (This installs the .NET 4.0 script mappings to a specific web) though again not sure if this is required by default. See: http://msdn.microsoft.com/en-us/library/k6h9cz8h.aspx
One more thing - If you're using REST (or an extension less URL mapping which I believe an MVC 4 web will use) - You'll need to add a "wild card" script mapping, which basically tells IIS to serve requests with no extension with the .NET 4.0 framework - See here However where they're referencing .NET 2.0 folders, you'll obviously want to reference the same files but in the .NET 4.0 folders :)
Thanks
I am new to SharePoint 2010. What is the main difference between sandbox and farm solution. Can you give me 5 differences to remember. I googled, but there is lot of matter to understand. As a start up guy, i want to know the basic difference.
Thanks for your help.
Farm Solution:
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm. When you debug a SharePoint project whose Sandboxed Solution property is set.
Sandbox solution:
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution. Because sandboxed solutions do not run in the IIS worker process, neither the IIS application pool nor the IIS server must restart. Visual Studio attaches the debugger to the SPUCWorkerProcess process that the SPUserCodeV4 service in SharePoint automatically triggers and controls. It is not necessary for the SPUCWorkerProcess process to recycle to load the latest version of the solution.
For more please refere this link
You can also refere this to know sandbox solutions goodlink
Farm Solutions:
Farm solutions are hosted in the IIS worker process (W3WP.exe).
If you run any code in farm solution the whole farm will got affected.
If you deploy any feature or retract any feature the whole application pool got recycled.
Since they are scoped as farm level, they have full trust access to all the resources.
When the Sand boxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
Sand boxed Solution:
Sand boxed solutions are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe).
try to this link
- The process runs under a CAS policy that restricts programmatic access to any resource outside the sandbox.
- So it never restart the IIS application pool.
- If you run any code it will affect only the site collection of the solution.
- Helpful if you have shared hosting.
- When the Sandboxed Solution property is set to True, selecting Build\Deploy Solution deploys the solution to the site collection Solution Gallery.
One major difference in the deployment is Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
This Link http://www.enjoysharepoint.com/Articles/Details/differences-between-sandboxed-and-farm-solutions-i-66.aspx
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm.
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution.
(from http://msdn.microsoft.com/en-us/library/ee361616.aspx)
One major difference is we can't create Aplication pages in Sandbox solutions.Beacuse Application pages are stored in the 14\TEMPLATES\_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
Also we cant create VISUAL web parts in Sandbox soultions.
We cant use code to connect to the external web services or to database in the sandbox soltion
Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
Normally we are using Sandbox solution for Online sharepoint such as office365. In this case user will get a solution to work with, but not the Physical system folders. So we cant give any images or contents into the Layout folder(it is restricted). And the main thing is We couldn't able to use some SP-class features in the Sandbox solution(which can be get the information about other farm solutions and server information). Thus farm solution is restricting this SP classes, system folders along with SPUCWorkerProcess process.
We can create the Visual Webparts as Sandbox solutions in 2013 but we have to make sure about the classes and we never want to use the layout folders etc.
Farm Solutions properties:
Farm solutions are hosted in the IIS worker process (W3WP.exe).
If you run any code in farm solution the whole farm will got affected.
If you deploy any feature or retract any feature the whole application pool got recycled.
Since they are scoped as farm level, they have full trust access to all the resources.
When the Sand boxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.
One major difference is we can't create Aplication pages in Sandbox solutions.Beacuse Application pages are stored in the 14\TEMPLATES_LAYOUTS and when we deploy as sandbox we dont have permissions to the physical folder.
Also we cant create VISUAL web parts in Sandbox soultions.
We cant use code to connect to the external web services or to database in the sandbox soltion
Farm solutions are installed and deployed. Sandboxed solutions are uploaded and activated.
Farm solutions, which are hosted in the IIS worker process (W3WP.exe), run code that can affect the whole farm.
Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution.
Please look the website that contains more details about the Farm Solutions and Sandbox Solution details :
http://www.techcontents.com/uncategorized/difference-farm-solutions-sandbox-solutions-sharepoint-2010/
I'm wanting to scan files a user uploads to our websites on the server-side. I'd prefer it to be something we can run on-demand that doesn't have to be running all the time on the server. What solutions are available for Windows Server 2008 R2? Which products specifically would you recommend?
If I were in your situation, I would script up a solution to call ClaimAV on the file, whenever you receive the file. For Windows, if you are running IIS, (or any web framework) there is probably some sort of callback on file reception you can plug this into.
Almost all the antivirus programs provide you a command-line version (or starting parameters) to scan just one file, or a directory.
There are several scanners on demand, there is a list named "Probably the Best Free Security List in the World" which lists a few, sorry I cannot provide the link because StackOverflow limits the amount of hyperlinks new users can post.
Although not listed in that list, one of the best I've used is the F-Prot Antivirus and it seems it runs well in Windows Server 2008
https://forum.f-prot.com/index.php?topic=1691.0
Cheers
For your case the best solution would be using http://www.virustotal.com/