I tried the starter-kit Personal Website. It runs fine locally and runs at the hosted webspace.

But the published website lacks all 'spice":

- there is no background colour

- Labels and textboxes are not correctly arranged

- Navigation entries are simply the words in line without any layout

I thought there must be something with 'master.default', but I can't find anything.

Any hints what to do?

Thanks in advance!

gebhard

Hi,

The problem might be style sheets, check whether style sheets are loaded or not.Try to apply your own set of Styles if no styles defined.

Well it seams that you are missing you css file. This is my best bet.

Hi Kumar,

the directories App_Themes, Black, White, Images and the files Default.css, Default.skin and Frame.css are there.

Regards

Gebhard

Hi Denis,

as I just wrote to Kiran. The CSS-Files are there.

I can't find any difference - execept the "connections" - between the local and the hosted application.

Regards

Gebhard

What is the Url to your hosted site, maybe if we see what is happening someone can come up with an answer. 

Try to check in your HTML page's source whether there is a <link....> tag with the CSS files or not.

The first one is : http://www.an1.bluesys.com/an1/default.aspx
It's the Personal Web Starterkit: it should look like: http://starterkits.asp.net/PersonalWebsite/

The second one is : http://www.an2.bluesys.com/an2/default.aspx
It's Microsoft's CssAdaptersTutorial, it should look like: http://www.asp.net/CssAdapters/Default.aspx

Locally at the ASP.NET Development Server both applications run quite well.

The first application does not contain a "<link...> tag with the CSS files.

The second application has the link:

<link runat="server" rel="stylesheet" href="~/CSS/Import.css" type="text/css" id="AdaptersInvariantImportCSS" />
<!--[if lt IE 7]>
    <link runat="server" rel="stylesheet" href="~/CSS/BrowserSpecific/IEMenu6.css" type="text/css" id="IEMenu6CSS" />
<![endif]-->

gebhard:

The first one is : http://www.an1.bluesys.com/an1/default.aspx
It's the Personal Web Starterkit: it should look like: http://starterkits.asp.net/PersonalWebsite/

The second one is : http://www.an2.bluesys.com/an2/default.aspx
It's Microsoft's CssAdaptersTutorial, it should look like: http://www.asp.net/CssAdapters/Default.aspx

Locally at the ASP.NET Development Server both applications run quite well.

This might sound weird but your site is doing some kind of redirection which is most likely the issue for both sites.

If you enter http://www.an1.bluesys.com it redirects to http://www.an1.bluesys.com/an1/ (which throws a 404 error to boot, I assume that this folder does not have the default.aspx page as one of the default pages for the web site).  The issue is that the themes support is looking at the url from the root of the site or http://www.an1.bluesys.com not http://www.an1.bluesys.com/an1/ .  To see what I mean click on this http://www.an1.bluesys.com/App_Themes/White/Frame.css you should start to download the white frame.css file.  Everything is in the right place but the configuration of the site is messing things up.

Hopefully this makes some sense.

This might sound weird but your site is doing some kind of redirection which is most likely the issue for both sites.

The redirection is necessary because all domains point to the root of the hosted webspace. Each domains has its own folder and in the root
a default.aspx - page does the redirection:

<script type="text/javascript">
 var httphost =document.location.hostname.replace(/www./,"");
 switch(httphost) {
 ...
 case "an1.bluesys.com":
 document.location = " /an1";
 break;
 }
 </script>

That is what I figured when I went to the site.  There are two ways you can solve this issue (maybe more but these two off the top of my head right now) one depends on how much control your hosting company has over your webspace root folder.

1. The harder of the two would be to have all websites point to a separate folder in your hosted webspace root (including subdomains).  This way you don't need a web site in the root folder just in the subfolders (this is how I have mine setup).  Again this depends on how much control over your webspace you have.
2. The other option is setting up virtual folders under the root.  I am not a big fan of it and I probably cannot offer any real advice since I don't do it often enough.  The problem I have had with virtual folders is getting the behaviour of the local setup and "live" setup to work the same.

Hopefully one of these options can solve your issue.

whighfield:

The harder of the two would be to have all websites point to a separate folder in your hosted webspace root (including subdomains). 

After a long struggle the problem is now solved. All my websites pointed to a separate folder and in the root I used a script for redirection. That worked quite well

with HTML-Websites for years. Now my provider told me that  ASP.NET-Websites must *not* point to the separate folder but to the root. The redirection (to the separate

folders) must be done by a script in the root. So there are three points:

1. all websites point to the root of the hosted webspace,

2. all websites have a separate folder,

3. a script in the root redirects the websites to their folders.

Thanks for your help!