locked
small basic and windows 8 RRS feed

  • Question

  • Hi  Everyone,

    I'm William, but just call me Bill.

    I recently installed small basic on a windows 8 laptop.  I now have windows 8.1.

    I became a member of the facebook group of small basic enthusiasts, and noticed several were having problems installing and using small basic on windows 8.

    I told them they needed the 3.5 .net framework, but when I searched for the .NET framework in my control panel I found 4.5 and 4.5.1

    Would it be correct to say they need to install the 3.5 even if they have the 4.5?

    Small Basic is great, runs well for me; and is not a toy at all like the first basic I used 40 years ago.

    Are there any other suggestions you can offer?

    Thanks for your help.

    Sunday, December 29, 2013 3:47 AM

Answers

  • I've already replied to that same question many times already! :D

    Small Basic v1.0 was compiled in .Net Framework 3.5 SP1. Thus it demands that particular Virtual Machine to be already properly installed in order to run it!

    Now some caveats: A higher .Net Framework version CAN'T run programs which were compiled by previous lower versions! Each number version is unique in its own resources.

    Now, each Microsoft's OS version can come w/ different bundled .Net Framework versions pre-installed. Or even none at all!

    If some1 got Windows 7, they can rest assured .Net Framework 3.5 SP1 and even .Net Framework 2 are already properly pre-installed!

    For Vista users, even though it already comes w/ .Net Framework 3.5, yet it's not its upgraded SP1 version. So an update is needed to get Small Basic running there!

    For Windows XP, AFAIK, there's no bundled .Net Framework pre-installed. Thus in order to run any .Net-based app that shows up, it's good advice to preemptively install .Net 2, .Net 3.5 SP1 and .Net 4.5 there to have it all and avoid any hassles!  ;-)

    And it seems like that for both Windows 8 & 8.1, Microsoft's decided to have latest .Net Framework 4.5 pre-installed only. Even though most .Net-based apps are still .Net 3 or .Net 2!


    Click on "Propose As Answer" if some post solves your problem or "Vote As Helpful" if some post has been useful to you! (^_^)

    • Proposed as answer by litdev Sunday, December 29, 2013 10:28 PM
    • Marked as answer by Nonki Takahashi Tuesday, January 7, 2014 12:08 AM
    Sunday, December 29, 2013 11:21 AM
    Answerer
  • Hey thanks goto, again :).  I finally get it. What confused me was that I couldn't find 3.5 in explorer.

    Just passing this on:

    A Yarrell just pointed out something helpful as well that people can check: Control panel > Programs > turn windows features on or off. Mine is partially checked, win7:

    So I reckon if you've got this issue then:

    1. check your windows features settings;
    2. if no option available then d/load .NET 3.5;
    3. if still issue after d/load then recheck step 1.
    • Edited by Jibba j Sunday, December 29, 2013 6:50 PM add steps
    • Marked as answer by Nonki Takahashi Tuesday, January 7, 2014 12:08 AM
    Sunday, December 29, 2013 1:17 PM

All replies

  • Hi Bill

    I run on Win7 and only have .Net4.5 installed. I can't see any evidence of 3.5 on my pc. Everything runs fine.

    Here's an earlier thread where this sort of came up: http://social.msdn.microsoft.com/Forums/en-US/38e52ff0-11c2-4426-aef8-6ca7218fbca3/small-basic-installation-files?forum=smallbasic

    If all else fails I suppose one could try 3.5 and see what happens.

    Sunday, December 29, 2013 7:55 AM
  • Also, in my case I originally had 3.5 then updated to 4.5.

    All prior posts on this suggest yes to 3.5. I not so sure.

    Here's a pic of my installed programs for dot net. 3 files.

    • Edited by Jibba j Sunday, December 29, 2013 8:09 AM pic
    Sunday, December 29, 2013 8:02 AM
  • I've already replied to that same question many times already! :D

    Small Basic v1.0 was compiled in .Net Framework 3.5 SP1. Thus it demands that particular Virtual Machine to be already properly installed in order to run it!

    Now some caveats: A higher .Net Framework version CAN'T run programs which were compiled by previous lower versions! Each number version is unique in its own resources.

    Now, each Microsoft's OS version can come w/ different bundled .Net Framework versions pre-installed. Or even none at all!

    If some1 got Windows 7, they can rest assured .Net Framework 3.5 SP1 and even .Net Framework 2 are already properly pre-installed!

    For Vista users, even though it already comes w/ .Net Framework 3.5, yet it's not its upgraded SP1 version. So an update is needed to get Small Basic running there!

    For Windows XP, AFAIK, there's no bundled .Net Framework pre-installed. Thus in order to run any .Net-based app that shows up, it's good advice to preemptively install .Net 2, .Net 3.5 SP1 and .Net 4.5 there to have it all and avoid any hassles!  ;-)

    And it seems like that for both Windows 8 & 8.1, Microsoft's decided to have latest .Net Framework 4.5 pre-installed only. Even though most .Net-based apps are still .Net 3 or .Net 2!


    Click on "Propose As Answer" if some post solves your problem or "Vote As Helpful" if some post has been useful to you! (^_^)

    • Proposed as answer by litdev Sunday, December 29, 2013 10:28 PM
    • Marked as answer by Nonki Takahashi Tuesday, January 7, 2014 12:08 AM
    Sunday, December 29, 2013 11:21 AM
    Answerer
  • Also, in my case I originally had 3.5 then updated to 4.5.

    .Net Framework 3.5 can't be upgraded to 4.5. At most to 3.5 SP1!

    Merely you've installed .Net 4.5 along w/ Win7's pre-bundled .Net 3.5 & .Net 2. And possibly .Net 1.1 too !  :D


    Click on "Propose As Answer" if some post solves your problem or "Vote As Helpful" if some post has been useful to you! (^_^)

    Sunday, December 29, 2013 12:25 PM
    Answerer
  • Hey thanks goto, again :).  I finally get it. What confused me was that I couldn't find 3.5 in explorer.

    Just passing this on:

    A Yarrell just pointed out something helpful as well that people can check: Control panel > Programs > turn windows features on or off. Mine is partially checked, win7:

    So I reckon if you've got this issue then:

    1. check your windows features settings;
    2. if no option available then d/load .NET 3.5;
    3. if still issue after d/load then recheck step 1.
    • Edited by Jibba j Sunday, December 29, 2013 6:50 PM add steps
    • Marked as answer by Nonki Takahashi Tuesday, January 7, 2014 12:08 AM
    Sunday, December 29, 2013 1:17 PM