Blank page - Publishing

Answered Closed
0
0

Hi!

 

I’m trying to publish my first test page on remote IIS server, but I got a blank page. Everything is OK when I run it on VS2015.

 

http://www.cappato.com.br/wisej/

 

May you help me, please?

 

Thanks,

Ulisses.

Attachment
  • You must to post comments
Best Answer
0
0

Hi Ulisses,

I can confirm what you reported. At the moment Wisej cannot work in medium trust. In fact very little works with IIS in medium trust. Data binding, just to mention one feature, doesn’t work without reflection which doesn’t work in medium trust. We also need to write to the temp path (this can be changed). Serialization doesn’t work.

It looks like Microsoft itself is discouraging medium trust since it really doesn’t work. Not even azure sites are in medium trust.

https://stackoverflow.com/questions/16849801/is-trying-to-develop-for-medium-trust-a-lost-cause

https://support.microsoft.com/en-us/help/2698981/asp.net-partial-trust-does-not-guarantee-application-isolation

We started following the security exceptions to try to resolve them, but it’s too deep into .NET itself.

Sorry I can’t change this.

Best,

Luca

  • Ulisses
    Thanks, Luca. I will move my website to another provider.
  • You must to post comments
0
0

Luca:

I checked in my IIS that Wisej works in full trust level only. My provider limits it to medium trust level.

May you help about it, please?

Thanks,

Ulisses.

  • You must to post comments
0
0

Luca:

I’m verifying with my provider what is occurring. It’s OK in my IIS (localhost). I asked him about ARR.

My provider limits .NET applications to medium trust level. Any problem in this case?

Thanks,

Ulisses.

  • You must to post comments
0
0

Luca:

I added wisej.wx file to root and wisej folder.

http://www.cappato.com.br/wisej.wx

File content is not appearing… Should I configure MIME or add entries to my web.config?

Thanks.

  • Luca (ITG)
    The problem is not the file, there is no wisej.wx file. *.wx is the extension used by the handler (in web.config) like all web services. If the ARR checks for the existence of a file, or if it caches files, or if it’s not routing requests for *.wx resources then your web site can only serve static files or only the dynamic extensions that are recognized. Can you try with an IIS server without ARR?
  • You must to post comments
0
0

Luca:

 

My publishing isn’t building WX files, only Default.html, Default.json and Web.config… more bin DLLs…

 

Where is the bootstrapper?

 

Thanks.

  • Luca (ITG)
    *.wx is the extension used by the wisej handler, see entry in web.config. There are no .wx files, it’s just a router extension exactly like .ashx for asp.net services, or .axd, etc. If your server is behind an ARR you need to make sure the ARR routes *.wx URLs. I’m not familiar with Microsoft ARR. The bootstrapper is a very small javascript script that loads the large javascript scripts. All wisej is to the browser is javascript.
  • You must to post comments
0
0

I just tried but it doesn’t return anything. I thought it may have been the “/wisej” application name that could confuse the handler with the wisej.wx url so I tried to create a new “/wisej” app on our demo server but it works fine.

It looks like /wisej is  sub site in IIS, and there can be problems with the inherited web.config from the parent site. To test that the configuration is correct you have to be able to query http://yoursite.com/wisej.wx. In your case http://www.cappato.com.br/wisej/wisej.wx and you should get this:

http://demo.wisej.com/wisej/wisej.wx

Which is the bootstrapper.

I noticed that your site has this header: X-Powered-By: ARR/2.5

Is it Microsoft Application Routing? Maybe it’s not routing *.wx URLs?

  • You must to post comments
0
0

Luca:

 

My website is back.  Application pool is started and .NET 4.5 integrated pipeline is OK.

 

May you access it again?

 

Thanks!

  • You must to post comments
0
0

Looks like your web server is down. It returns 503 for anything, even then main IIS default page. Make sure the application pool is started and it’s for .NET 4.5 integrated pipeline, and that the IIS service is started.

  • You must to post comments
Showing 8 results