167

I'm using Windows 10 and I'm sure Windows 11 isn't out yet

Comments
  • 25
    That's Microsoft's equivalent of a "fuck you" to all who don't update Windows.
  • 3
    I won't even bother to fix this
  • 1
    An outdated version of Windows? 😋
  • 2
    Ikr. Im using the latest 1703 Creator's Update. Oh well
  • 7
    @devmonster Maybe it wants you on the Insider Program 😂
  • 3
    U need to update ur windows bro ! ... Newer dev features aren't available on older versions ... It's like if u're targeting ur application to higher Builds than ur own PC, u'll get this message !
  • 2
    Best temporary solution wud be to target ur application upto ur own Build (say Anniversary update)
  • 4
    @Prk123 but... but... i'm on the latest public release 😫
  • 3
    @devmonster can u tell me ur Build Version ?
  • 1
    @Prk123 my VS is 14.0.25431.01 update 3

    Win10 is build 15063.483
  • 1
    Had the same f❤cking problem. That's why I switched to Linux
  • 0
    You need the creators update!
  • 2
    so you are developing an application that target a Windows version that you haven't installed and the problem is windows right?
  • 0
    @rtfm how exactly this will solve the problem? And of course will not bring new problems, right?
  • 1
    @vojb i am on the Creators Update :)
  • 0
    Did you install and targeting an sdk version higher than your windows version?
  • 0
    @domresc this is a Xamarin app solution. I think it's just an issue with the rendering of Xaml
  • 1
    @rtfm Installing Linux would not solve anything in this case 😂
  • 1
    @rtfm let's assume that you'll not have driver, crash, freeze, random problems ... how do you plan to work with .net (not core) ?
  • 1
    @rtfm Well seeing as Visual Studio doesn't run on Linux...
  • 0
    Hello @devmonster, check the target and the minimum version of the windows app solution.
    Anyway I'm too a Xamarin developer.
  • 1
    @domresc hehe i think it's just a bug. I accidentally added a Xaml file instead of a Content View and that's how Vs reacts when you open it
  • 0
    @devmonster mmm i wouldn't call it a bug, consider that for xamarin. Forms and uwp/wpf we use xaml files,it can't undrrstand everything :)
  • 0
    @dontbeevil i added the file using VS. You'd think it would understand the file formats it knows
  • 2
    @devmonster not really, vs gives you some freedom to add different type of files, because you could use it somehow, the rest is up to you :) I wouldn't call it totally a bug, maybe could be implemented in some more helpful way
  • 1
    @dontbeevil just so we are on the same xaml page here, I added the file from VS Add New File menu, selected Xaml Page from the available templates on the New File screen. That implies it's a file type it knows how to handle.

    I understand that VS can open any type of text or nontext file; it is an editor afterall. But wouldn't it be weird if for instance MSWord offers to create a DOT file and then suddently says "oh I don't know how to open that"

    And of course third party add ons can add new type of templates that VS might not know how to open but let's be real - This is a xaml file. Any particular reason why VS can't fall back to text only format?
  • 2
    @devmonster You can write click the file on Solution Explorer and Open With VS' text editor

    I had a controller file that got stuck in design view once
    This was the only way I could open and edit the file:(
  • 0
    @itsdaniel0 of course that will work hehe. I just find it weird that it got confused handling xaml. Im starting to get angry at VS more and more lately since it likes to crash a lot
  • 1
    Maybe they check for winver >= 98?
  • 0
    Run it in compatibility mode? (shrug)
  • 0
    11?? Really?? Last time I checked, MS couldn't count
  • 0
Add Comment