<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title><![CDATA[LiquidSix Hosting]]></title>
<link><![CDATA[https://support.liquidsix.com/]]></link>
<description />
<generator><![CDATA[Kayako fusion v4.72.0]]></generator>
<item>
<title><![CDATA[Do you have the IonCube loaders installed?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/33]]></link>
<guid isPermaLink="false"><![CDATA[182be0c5cdcd5072bb1864cdee4d3d6e]]></guid>
<pubDate><![CDATA[Sat, 02 Dec 2006 04:35:02 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, the ionCube loaders are installed on all of our hosting servers, and available for your use.]]></description>
<content:encoded><![CDATA[Yes, the ionCube loaders are installed on all of our hosting servers, and available for your use.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you have Zend Accelerator installed?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/32]]></link>
<guid isPermaLink="false"><![CDATA[6364d3f0f495b6ab9dcf8d3b5c6e0b01]]></guid>
<pubDate><![CDATA[Sat, 02 Dec 2006 04:35:02 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, Zend acclerator is available for your use on all of our hosting servers.]]></description>
<content:encoded><![CDATA[Yes, Zend acclerator is available for your use on all of our hosting servers.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support ASP.Net 1.0?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/39]]></link>
<guid isPermaLink="false"><![CDATA[d67d8ab4f4c10bf22aa353e27879133c]]></guid>
<pubDate><![CDATA[Sat, 02 Dec 2006 04:35:02 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[ASP.Net 1.0 is not installed on our servers, however ASP.Net 1.1 is backwards compatiable and is available on our servers instead. Almost all ASP.Net 1.0 scripts will run fine on 1.1.]]></description>
<content:encoded><![CDATA[ASP.Net 1.0 is not installed on our servers, however ASP.Net 1.1 is backwards compatiable and is available on our servers instead. Almost all ASP.Net 1.0 scripts will run fine on 1.1.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support ASP.Net 1.1?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/38]]></link>
<guid isPermaLink="false"><![CDATA[a5771bce93e200c36f7cd9dfd0e5deaa]]></guid>
<pubDate><![CDATA[Sat, 02 Dec 2006 04:35:02 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, ASP.Net 1.1 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net 1.1 is available on your hosting plan, or whether you need to upgrade.]]></description>
<content:encoded><![CDATA[Yes, ASP.Net 1.1 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net 1.1 is available on your hosting plan, or whether you need to upgrade.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support ASP.Net 2.0?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/37]]></link>
<guid isPermaLink="false"><![CDATA[a5bfc9e07964f8dddeb95fc584cd965d]]></guid>
<pubDate><![CDATA[Sat, 02 Dec 2006 04:35:02 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, ASP.Net 2.0 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net 2 is available on your hosting plan, or whether you need to upgrade.

To switch between versions of ASP.Net on your domain, go to "W...]]></description>
<content:encoded><![CDATA[Yes, ASP.Net 2.0 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net 2 is available on your hosting plan, or whether you need to upgrade.<br />
<br />
To switch between versions of ASP.Net on your domain, go to "Website Settings", a link to which is found on your domain page in Helm.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support ASP.Net MVC? (Model View Controller)]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/82]]></link>
<guid isPermaLink="false"><![CDATA[9778d5d219c5080b9a6a17bef029331c]]></guid>
<pubDate><![CDATA[Mon, 14 Dec 2009 22:38:56 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, MVC sites can be hosted with us.  In order to avoid versioning issues and allow users to use whatever version of MVC they wish, we do not preinstall it on the servers. Instead, simply upload your choice of System.Web.Mvc.dll (or Microsoft.Web.Mvc.dll...]]></description>
<content:encoded><![CDATA[<p>Yes, MVC sites can be hosted with us.<br /> <br /> In order to avoid versioning issues and allow users to use whatever version of MVC they wish, we do not preinstall it on the servers. Instead, simply upload your choice of System.Web.Mvc.dll (or Microsoft.Web.Mvc.dll as needed) to the "bin" directory of your website. No further action is required in order to run an MVC site.<br /> <br /> MVC also has a facility to allow for routing, for SEO friendly URLs. This requires the use of a wildcard script mapping for ASP.Net. If you understand the effects of this, and wish to enable it on your account, this can be done from "Website Settings" in Helm.</p>
<p>Many MVC sites based on more recent versions require full trust in order to function, as well as using integrated pipeline. These settings are not set by default, but can be set for free at any time from the "Website Settings" page for the domain in your control panel.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support the .Net framework 3.0?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/70]]></link>
<guid isPermaLink="false"><![CDATA[7cbbc409ec990f19c78c75bd1e06f215]]></guid>
<pubDate><![CDATA[Fri, 30 May 2008 02:39:42 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, the .Net Framework 3.0 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net is available on your hosting plan, or whether you need to upgrade.

To switch between versions of ASP.Net on your domain,...]]></description>
<content:encoded><![CDATA[Yes, the .Net Framework 3.0 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net is available on your hosting plan, or whether you need to upgrade.<br />
<br />
To switch between versions of ASP.Net on your domain, go to "Website Settings", a link to which is found on your domain page in Helm.]]></content:encoded>
</item>
<item>
<title><![CDATA[Do you support the .Net framework 3.5?]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/71]]></link>
<guid isPermaLink="false"><![CDATA[e2c420d928d4bf8ce0ff2ec19b371514]]></guid>
<pubDate><![CDATA[Fri, 30 May 2008 02:40:00 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Yes, the .Net Framework 3.5 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net is available on your hosting plan, or whether you need to upgrade.

To switch between versions of ASP.Net on your domain,...]]></description>
<content:encoded><![CDATA[Yes, the .Net Framework 3.5 is installed on our servers. Check the plan you have purchased (or are interested in) to see if ASP.Net is available on your hosting plan, or whether you need to upgrade.<br />
<br />
To switch between versions of ASP.Net on your domain, go to "Website Settings", a link to which is found on your domain page in Helm.]]></content:encoded>
</item>
<item>
<title><![CDATA[Hosting .Net Core Applications (also known as ASP.Net Core or ASP...]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/108]]></link>
<guid isPermaLink="false"><![CDATA[a3c65c2974270fd093ee8a9bf8ae7d0b]]></guid>
<pubDate><![CDATA[Thu, 02 Mar 2017 20:50:42 +0000]]></pubDate>
<dc:creator />
<description><![CDATA[From March 2017, all LiquidSix Hosting hosting plans that support ASP.Net also support the new .Net Core from Microsoft. You can develop .Net Core applications using Visual Studio or other tools. This knowledgebase article covers the steps to host your ne...]]></description>
<content:encoded><![CDATA[<p>From March 2017, all LiquidSix Hosting hosting plans that support ASP.Net also support the new .Net Core from Microsoft. You can develop .Net Core applications using Visual Studio or other tools. This knowledgebase article covers the steps to host your new application with us once it has been developed.</p>
<p>Once you have developed the application, you can use Visual Studio (or an alternative) to publish it to a directory on your computer. This will contain directories such as "bin", "refs" and "wwwroot" (amongst others) and files including a "web.config" and "appsettings.json".</p>
<p>The web.config file should look something like this:</p>
<pre class="csharp" title="Click to copy to clipboard"><span style="font-family: 'courier new', courier; color: #000080;">&lt;?xml version="1.0" encoding="utf-8"?&gt;<br />&lt;configuration&gt;<br /> &lt;!--<br /> Configure your application settings in appsettings.json. Learn more at http://go.microsoft.com/fwlink/?LinkId=786380<br /> --&gt;<br /> &lt;system.webServer&gt;<br />   &lt;handlers&gt;<br />     &lt;add name="aspNetCore" path="*" verb="*" modules="AspNetCoreModule" resourceType="Unspecified" /&gt;<br />   &lt;/handlers&gt;<br />   &lt;aspNetCore processPath="dotnet" arguments=".\WebApplication1.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" forwardWindowsAuthToken="false" /&gt;<br /> &lt;/system.webServer&gt;<br />&lt;/configuration&gt;<br /><br /></span></pre>
<p>You should not need to change anything in this file, however is may be useful to understand it's construction. The handlers section will tell the server to use ASP.Net core. The configuration below sets details about how the application will be run, however for security reasons, a lot of the fields are ignored on our shared hosting and the defaults will be used. The following settings are ignored:</p>
<ul>
<li>processPath</li>
<li>startupTimeLimit</li>
<li>shutdownTimeLimit</li>
<li>requestTimeout</li>
<li>processesPerApplication</li>
<li>rapidFailsPerMinute</li>
</ul>
<p>The most important setting is the "arguments" one, which specifies the DLL that contains your application. This one must exist in the file, and Visual Studio should have included it.</p>
<p>Another file you may need to look at is "appsettings.json". This includes the database connection strings if your application uses a database, and so you may need to edit these in order to point them at our database server instead of your own local development server. The connection string would be the same as for a non-.Net core application.</p>
<p>Once you have these files correct, you can upload the application to our server. Connect via FTP in the normal way, and upload all of the files (including all DLLs) from your application directory to the "wwwroot" folder in FTP. Although they have the same name, our "wwwroot" folder is different to the one in your application, and your one will end up inside the server one.</p>
<p>When the files are uploaded, the only thing left to do is to enable .Net core on your website. To do that, login to your hosting control panel with us and click on "Domains", then your domain, then click "Website Settings". Ensure that ASP.net is enabled, and then select ".Net Core" from the dropdown box for the ASP.Net version. Please note that when using .Net core on a domain, you can not use other ASP.Net files on the same domain.</p>
<p>That's it, your application should now be working! If you have any problems or suggestions with the new .Net core support, please contact us in the normal way.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[HOWTO: Setup a directory as an IIS Application]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/69]]></link>
<guid isPermaLink="false"><![CDATA[14bfa6bb14875e45bba028a21ed38046]]></guid>
<pubDate><![CDATA[Fri, 30 May 2008 02:34:37 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[Some ASP or ASP.Net applications must be run in a directory that is an IIS application in order to function properly. If you run these applications in the root of your domain, this is automtically an IIS application. If, however, you run the application i...]]></description>
<content:encoded><![CDATA[Some ASP or ASP.Net applications must be run in a directory that is an IIS application in order to function properly. If you run these applications in the root of your domain, this is automtically an IIS application. If, however, you run the application in a subdirectory you will need to set this as an IIS application first.<br />
<br />
In the instructions below, we setup the directory "Directory1" as an IIS application. You can replace the name as appropriate.<br />
<br />
1. Login to the Helm control panel, and navigate to the domain.<br />
2. Click on "Virtual Directories" and then "Add New".<br />
3. Enter "\" into the "Path To Virtual Directory"<br />
4. Enter "Directory1" into the "Virtual Directory Name"<br />
5. Then enter "\Directory1" into the "Physical Folder" and press save.<br />
<br />
Your IIS application is now setup and ready to use!]]></content:encoded>
</item>
<item>
<title><![CDATA[I need an ASP.Net Wildcard Script Mapping]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/94]]></link>
<guid isPermaLink="false"><![CDATA[f4b9ec30ad9f68f89b29639786cb62ef]]></guid>
<pubDate><![CDATA[Sun, 30 Sep 2012 17:03:04 +0000]]></pubDate>
<dc:creator />
<description><![CDATA[If you are using URLs in ASP.Net that end in anything other than the normal extensions (.aspx, .ashx etc) then you will need a wildcard script mapping. It is important to understand the effects of this, so that it doesn't cause issues with anything else y...]]></description>
<content:encoded><![CDATA[<p>If you are using URLs in ASP.Net that end in anything other than the normal extensions (.aspx, .ashx etc) then you will need a wildcard script mapping. It is important to understand the effects of this, so that it doesn't cause issues with anything else you may have on the site.</p>
<p>To enable it, click on the "Website Settings" page for the domain and use the checkbox at the bottom.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Using ISAPI Rewrite with Wordpress]]></title>
<link><![CDATA[https://support.liquidsix.com/index.php?/Knowledgebase/Article/View/83]]></link>
<guid isPermaLink="false"><![CDATA[fe9fc289c3ff0af142b6d3bead98a923]]></guid>
<pubDate><![CDATA[Fri, 19 Mar 2010 19:16:41 +0000]]></pubDate>
<dc:creator><![CDATA[Paul Woodland (Import)]]></dc:creator>
<description><![CDATA[ISAPI Rewrite is an optional feature on our hosting plans. To configure it for use with Wordpress enter the following permalink code in wordpress setup:
/%postname%

Then create a .htaccess file in the wwwroot directory containing the following code:
...]]></description>
<content:encoded><![CDATA[ISAPI Rewrite is an optional feature on our hosting plans. To configure it for use with Wordpress enter the following permalink code in wordpress setup:<br />
/%postname%<br />
<br />
Then create a .htaccess file in the wwwroot directory containing the following code:<br />
<br />
RewriteBase /blog/ <br />
RewriteCond %{REQUEST_FILENAME} !-f <br />
RewriteCond %{REQUEST_FILENAME} !-d <br />
RewriteRule ^(.*)/?$ index.php?p=$1 [NC,L]<br />
<br />
]]></content:encoded>
</item>
</channel>
</rss>