I have VS2017 Community edition installed in a Windows 7 PC and a Windows 10 laptop. They both have the exact same installation.
Last night I created a Cross-Platform > Mobile App (Xamarin.Forms) project in my Win10 laptop, and it ran perfectly in the android emulator. No issues there.
I did the same exact thing in my Windows 7 PC, and I'm getting tons of compiler errors. All of them are of the The type or namespace name 'System' could not be found nature.
Is there anything I need to do in Windows 7 so these projects run?
In both environments (Win7 and Win10) I did the exact same thing: installed VS2017, created the new Xamarin cross-platform project, and debugged it. In Win10 it runs flawlessly while in Windows 7 I get a bunch of compiler errors with System namespace, which is literally the most fundamental namespace of the .NET Framework.
Any help is appreciated.
I'd like to add that I created a regular ASP.NET Web Application in Windows 7 and it runs flawlessly (no issues with System namespace), so it's an error with Xamarin cross-platform.
The solution for compiling the solution successfully on my Windows 7 PC was to install .NET Framework 4.7.2
Related
I have a bunch of devices we sideloaded our app onto that are running windows 8.1
I was having problems with our project after I upgraded my dev machine to windows 10 so I created a new project using the standard blank project template. I then reimported my html/js code and started fresh.
This took care of the issues I was having but apparently the new template is only for window 10 and greater.
When I try to sideload onto a windows 8.1 machine it throws an error saying element:m does not meet the spec inside my appx package manifest.
I looked at both spec's but nothing is jumping out as being wrong, although there are differences.
I can't seem to find in the windows doc's what to do. Has anyone tried this?
What I want to do is create an app package for windows 8.1 machines from my windows 10 machine using Visual Studio 2015
Edited for clarity.
Has anyone used WTL on Windows 10 already? All applications that I create with WTL segfault on Windows 10. They work on Windows 8 and Windows 7.
I even tried the most basic Hello-World application in WTL on Windows 10 and it segfaults when I run it. There are no clear indications of what is wrong. The program just segfaults with generic Windows segfault error.
Looks like WTL isn't Windows 10 compatible yet? Has anyone had this problem yet.
Just asking here as others will probably have the same problem. I tried two different Windows 10 (pre-release beta, and official release). I'm using latest WTL version WTL 9.0.4140 Final (2014-05-30).
All of our commercial applications are WTL built in VS2008. They work fine on Windows 10. If you can get a dmp file you should be able to review the crash dmp in windbg and see what is causing the fault.
Windows 10 with Visual Studio 2015 Community compiles and runs WTL sample MemDlg, I used WTL91_5270_Beta
our commercial video application is WTL-based(vs2015 express).
work fine, but it act different to MFC-based applications.
when win10 menu popup, video frame-rate drop in MFC(26fps->10fps), WTL(26fps->5fps).
https://github.com/sailfish009/wtl (WTL Version 9.1 (build 5321 final) 2015-11-17)
I have developed an MFC SDI app, which uses the default CDocument Save, Save As and Load Menu Options. When I run this app on Windows XP, Vista, or 7 the app works fine - it can save and load documents without issue. When I run the same app on Windows 8 or 8.1 and click the Save option, the app crashes with a generic error message. Is there something extra that I need to install for it to work on Windows 8? Or is there something special I need to do to get an MFC SDI app to work on Windows 8?
I have tried to install Visual Studio on the Windows 8 machine to compile it there but I only have the Express version, which doesn't come with the MFC libraries, so it will not compile. The PC I wrote the app on, was a Windows 7 pc.
I am not too sure what other information might be useful.
EDIT:
The error message
I have managed to compile MFC applications in older versions of Visual Studio Express, see:
http://www.codeproject.com/Articles/30439/How-to-compile-MFC-code-in-Visual-C-Express
To get this to work in a recent VS Express will probably require some tinkering.
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.
I have VS2012 set up on Win7 32bit, WP8 and WP7.1 sdk set up, but whenever I try to create new project or add new WP8 project to existing solution i get this error.
http://i.stack.imgur.com/REAEM.png
I allso cannot use the feature described somewhere in webs to convert WP7 project to WP8 project, it just shots up as incompatible in solution explorer.
http://i.stack.imgur.com/GvbrR.png
Could you please point me to the problem?
You need Windows 8 to use the Windows Phone 8 SDK.
Supported operating systems: Windows 8, Windows 8 Pro
Operating system type:
Windows 8 64-bit (x64) client versions
http://www.microsoft.com/en-us/download/details.aspx?id=35471