I just converted an app from VS2008 to VS2010. But when I try to view the site in IE I get the message "Internet Explorer cannot display the webpage". This same app worked perfectly when I published the VS2008 version to the same folder. Any ideas?
The app uses .NET 4.0 which requires an IIS 7 App Pool using .Net 4, not 2. When I created a .Net 4 App Pool and assigned it to the app website the problem was resolved.
Related
I am working with Eclipse Kepler 4.3.2 and latest Worklight Studio downloaded and installed through Eclipse Marketplace (6.2.0.00-20140801-1709).
There are a lot of official IBM docs and web pages stating that WL 6.2 supports Win 8.1 hybrid store app development. At the same time, the IBM tutorials lead to complete the build cycle using MS Visual Studio 12 Express.
As long as I know, VS 12 targets Win 8 only, so VS 13 is needed to target Win 8.1 store apps.
So, after creating a new hybrid app, I add the Window 8 desktop and tablet environment (and the JSONStore optional feature also), then build that environment. At this point I use VS 2013 to open the .jsproj located in the windows8/native folder. VS 2013 notifies that the project must be retargeted from Windows 8 to Windows 8.1, then asks confirmation to make writable two read-only files: index.html and cordova.js. The reason for changing the content of these files during the migration from Win 8 to Win 8.1 is to change several references from "Microsoft.WINJS.1.0" to "Microsoft.WINJS.2.0".
At this point the Visual Studio project is fully functional, and also correctly runs on the Windows 8.1 tablet simulator. The noisy problem is that at every build of the windows8 environment Worklight regenerates index.html and cordova.js adding again the references to WinJS.1.0.
So, the question is: does the current Worlkight Studio version full supports Windows 8.1 development? Or, there is something wrong in my approach?
Worklight Studio is certified to work on Windows 8.1 using Visual Studio 2013.
From reading your question, and specificically this part:
At this point the Visual Studio project is fully functional, and also
correctly runs on the Windows 8.1 tablet simulator. The noisy problem
is that at every build of the windows8 environment Worklight
regenerates index.html and cordova.js adding again the references to
WinJS.1.0.
What I think is going on here is this:
You are creating your project in Worklight Studio and then open it in VS13 which then asks to migrate WinJS 1.0 to 2.0 and everything is working for you.
What you then do is re-build your project in Worklight Studio which brings back WinJS 1.0 as well as index.html
If you do changes in Visual Studio but do not bring them back into Eclipse, then your changes from VS will be lost. That is expected, because you are working with 2 IDEs, so you need to make sure that you copy back your code.
The template for a Windows8 app from Worklight Studio seems to be generating WinJS 1.0 regardless of targetting VS12 or VS13
So the only issue here is 2 above. It is worth investigating and it will be.
As for a "workaround", as long as you properly manage your code in 1, 2 should not prevent anything as you will still be given the option in VS to migrate to WinJS 2.0; it's an annoynace, though.
Is it possible to run Silverlight 5 application on 1and1.com hosting ?
After deploying the files and after browsing in place of the silverlight application I got the button "Get XML".
What I am doing wrong ?
According to http://faq.1and1.com/scripting_languages_supported/webconfig/2008/4.html the .xap is supported.
After contacting the support it turned out that I had the old Windows Hosting with Silverlight disabled.
After enabling it my application started without problems.
So yes. Silverlight 5 works only if you have Silverlight 5 plugin installed on your machine.
It seems that depends on the ability to download the .xap and to initialize the Silverlight object.
I have created an application installer for my MVC3 project and have followed the BIN Deployment suggestions found online.
My site has been installed but I don't get any pages displayed.
This is how the VS2010 installer project looks
and this is how I have IIS setup
How do you get the Home Index page to be the default page as it is when I run the application through Visual studio?
IIS 6.0 doesn't support extensionless urls out of the box. This means that if you try to navigate to /Home/Index, IIS 6.0 doesn't know that this is an ASP.NET application and nothing happens. Extensionless urls are supported out of the box starting from IIS 7.0 when running the application in managed pipeline mode.
You will need to associate the unmanaged aspnet_isapi.dll filter with ASP.NET if you want to achieve that. Phil Haack covered how this topic in his blog post (ASP.NET 4.0) and this post (for CLR 2.0, which is not your case since you are using ASP.NET MVC 3).
I am working on client's application in which we have two servers - development server and testing server. We first develop applications on development server and then publish it and host it on test server for client testing.
Testing server has Microsoft .NET framework 3.5 SP1. On development we have Visual Studio 2010.
We publish the website on development server using VS 2010 and then copy that folder to testing server and host it on its IIS.
Whenever we try access any aspx page of site hosted on testing server, we get error:
Could not load assembly App_Web_xxxxxx.dll". Make sure it is compiled before accessing the page
What can I do to resolve this?
This could be due to a lot of reasons.
I would start by trying one of the following things..
Make sure your IIS Site has the correct .net version specified - same as your application
Make sure you have all the required .net components installed in windows features (control panetl)
Look at event viewer for more errors and post it here
OK guys here is the solution.
Since my testing server is having Microsoft .NET framework 3.5 so on the development server while publishing from VS 2010, I have to choose target framework as 3.5.
Do this:
Right click web site -> Property Page -> Build -> Change the target framework.
After doing this setting, publish the web site again.
I am trying to publish an MVC 2 application to my local Win 7 IIS 7.
The app pool is Integrated 2.0, not classic.
The app is .net 3.5.
The project was originally started in VS2008, but I have upgraded to 2010.
I publish the app through the VS wizard to a file location, I have also tried publishing again in VS, but web deploy to localhost - neither makes a difference.
The app spins up fine when I just hit F5 in VS and work in debug mode.
Any ideas? I have googled about, but nothing has sorted it.
Thanks in advance.
Did you make sure the AppPool is set to allow 32bit apps?