Results 1 to 21 of 21

Thread: Licensing issues

  1. #1

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Licensing issues

    I just want to code on a free version of VB so I installed VB 2019. But eventually that version also ask me for a license key and would not allow me to keep using it. What is the solution?

  2. #2
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Since 2012, the Community edition of Visual Studio has been free. Whether VS 2019 or VS 2022, if you have installed the Community edition then you don't have to pay. If you have installed a different edition, uninstall it and install the Community edition. I don't use Community myself - I use Professional through work - so I'm not 100% sure how it works but, if it requires you to enter a license key, you can get one free from Microsoft and VS would instruct you how to do that. You can also probably license it through your Microsoft account, which you can also do with Professional. There may be some additional steps to link your MS account with VS but it is then just a matter of re-entering your credentials from time to time to refresh the license.

    If you are still having issues then try providing more relevant information, like a screenshot of exactly what you're seeing.

  3. #3

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    Attachment 188757

    Attached is a screenshot, I have clicked on every link and button here and it gives me no option to renew or buy a new license. Heck I am willing to pay a little dollars but there's no option here!

  4. #4
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    You're using the Enterprise edition, so that's obviously the issue. Even I can't use Enterprise because my company only has one license for it with our Microsoft subscription. Uninstall Enterprise and install Community, as I already suggested.

    BTW, based on that screenshot, you're using VS 2022, not 2019. That's no big deal and I would certainly suggest using the latest version unless you have a specific reason not to, but please make sure that you provide accurate information when posting here. It didn't matter this time but another time it might be a critical piece of information.

  5. #5

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    I was/am using 2019 but it just doesnt show up. I got 6.0 and 2010 express too and they dont show up either.

  6. #6
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    I don't what you're talking about. You posted about a problem with VS 2019 and then you posted a screenshot of VS 2022. If VS 2019 is the issue, why the screenshot of VS 2022 and no screenshot of VS 2019? If VS 2022 is the issue then why mention VS 2019 but not VS 2022? I don't understand the problem with clearly explaining the actual issue. If you provide inaccurate or misleading information then you're just making it less likely that you'll get the help you want.

    Anyway, if you're using any version of VS from 2012 onwards and you don't want to pay for it then install the Community edition. That's it, that's all. I said to do that in the first place and post a screenshot if you're still having issues but you then posted a screenshot without doing it. Ignoring advice when it's provided is another good way to reduce the likelihood of getting more help.

  7. #7
    Fanatic Member 2kaud's Avatar
    Join Date
    May 2014
    Location
    England
    Posts
    911

    Re: Licensing issues

    [When trying to open the attachment, I get an error "Invalid Attachment specified. If you followed a valid link, please notify the administrator" ]
    All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/

    C++23 Compiler: Microsoft VS2022 (17.6.5)

  8. #8

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    I was chatting with someone at microsoft and we talked about my problem and I brought up the idea of using 2019 and he agreed that would be a valid solution to not have to pay. I cant remember the exact website. That's why I have 2019 , but it still asks me for a key and prevents me from coding beyond a cutoff date that is today.

  9. #9
    PowerPoster PlausiblyDamp's Avatar
    Join Date
    Dec 2016
    Location
    Pontypool, Wales
    Posts
    2,301

    Re: Licensing issues

    Quote Originally Posted by PhotonBytes View Post
    I was chatting with someone at microsoft and we talked about my problem and I brought up the idea of using 2019 and he agreed that would be a valid solution to not have to pay. I cant remember the exact website. That's why I have 2019 , but it still asks me for a key and prevents me from coding beyond a cutoff date that is today.
    It looks like the issue is not the version of Visual studio 2019 vs 2022 but the edition - Community (free) vs Professional or Enterprise (both paid). If you want the free version then https://visualstudio.microsoft.com/vs/community/ is the latest and https://visualstudio.microsoft.com/vs/older-downloads/ will get you the older versions - just remember to install the Community edition if you want the free version.

    Unless you need VS 2019 though you may as well go for VS 2022 as it is the latest release.

  10. #10
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by PhotonBytes View Post
    I was chatting with someone at microsoft and we talked about my problem and I brought up the idea of using 2019 and he agreed that would be a valid solution to not have to pay. I cant remember the exact website. That's why I have 2019 , but it still asks me for a key and prevents me from coding beyond a cutoff date that is today.
    Judging by this thread, you gave that person at Microsoft incomplete or inaccurate information. They would have meant to install 2019 INSTEAD OF 2022 if 2022 wasn't working (which it was). Installing 2019 won't have any effect on your 2022 installation and that's what you showed in your screenshot. They are completely separate applications and have no bearing on each other. It is specifically that way so you can install multiple versions, which many people do. The issue, as has been said many times, was the fact that you installed the Enterprise edition, which costs thousands of dollars and generally only comes with a subscription. I told you in post #2 to install the Community edition if you hadn't already done so and that should have been the end of it. The problem hasn't changed and the solution hasn't changed.

  11. #11
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by 2kaud View Post
    [When trying to open the attachment, I get an error "Invalid Attachment specified. If you followed a valid link, please notify the administrator" ]
    That's interesting. I was expecting that to happen to me but it didn't. There is an issue with the Insert Image tool on the basic editor and the symptoms are what you describe. I've recently become a moderator so I can only assume that the issue doesn't affect accounts with the additional permissions.

    @PhotonBytes, for future reference, if you want to upload a screenshot, don't use that Insert Image tool. Click the Go Advanced button and then the Manage Attachments button and upload the image file like you would have to for other file types. That will enable all to see the image.

    Also, we don't need to see your entire screen when it's only one dialogue that is important. Screenshot software, including the Windows Snipping Tool, will allow you to specify a part of the screen to copy. Use that and include only what's relevant to the issue. You can specify an arbitrary rectangle or a specific window.

  12. #12

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    Quote Originally Posted by jmcilhinney View Post
    That's interesting. I was expecting that to happen to me but it didn't. There is an issue with the Insert Image tool on the basic editor and the symptoms are what you describe. I've recently become a moderator so I can only assume that the issue doesn't affect accounts with the additional permissions.

    @PhotonBytes, for future reference, if you want to upload a screenshot, don't use that Insert Image tool. Click the Go Advanced button and then the Manage Attachments button and upload the image file like you would have to for other file types. That will enable all to see the image.

    Also, we don't need to see your entire screen when it's only one dialogue that is important. Screenshot software, including the Windows Snipping Tool, will allow you to specify a part of the screen to copy. Use that and include only what's relevant to the issue. You can specify an arbitrary rectangle or a specific window.
    Well I was afraid that if I did that someone will say, you should provide us with more or all information so we can help you!

  13. #13

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    Quote Originally Posted by jmcilhinney View Post
    Judging by this thread, you gave that person at Microsoft incomplete or inaccurate information. They would have meant to install 2019 INSTEAD OF 2022 if 2022 wasn't working (which it was). Installing 2019 won't have any effect on your 2022 installation and that's what you showed in your screenshot. They are completely separate applications and have no bearing on each other. It is specifically that way so you can install multiple versions, which many people do. The issue, as has been said many times, was the fact that you installed the Enterprise edition, which costs thousands of dollars and generally only comes with a subscription. I told you in post #2 to install the Community edition if you hadn't already done so and that should have been the end of it. The problem hasn't changed and the solution hasn't changed.
    You don't seem to understand, we were trying to find a solution to me not wanting to pay to use Visual Studio. He gave me the impression that 2019 is free to use while 2022 is not.

    Am I on trial here? I think I am entitled to a phone call or a lawyer right?

  14. #14
    PowerPoster PlausiblyDamp's Avatar
    Join Date
    Dec 2016
    Location
    Pontypool, Wales
    Posts
    2,301

    Re: Licensing issues

    Quote Originally Posted by PhotonBytes View Post
    You don't seem to understand, we were trying to find a solution to me not wanting to pay to use Visual Studio. He gave me the impression that 2019 is free to use while 2022 is not.

    Am I on trial here? I think I am entitled to a phone call or a lawyer right?
    VS 2022 Community Edition is free to use - this was said in post #2, #4, #6, and #9 - the issue is you aren't actually appearing to listen to what people are saying. Have you tried installing the Community Edition of VS 2019 or 2022 and seeing what happens?

  15. #15
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by PhotonBytes View Post
    You don't seem to understand, we were trying to find a solution to me not wanting to pay to use Visual Studio.
    I understand that perfectly well.
    Quote Originally Posted by PhotonBytes View Post
    He gave me the impression that 2019 is free to use while 2022 is not.
    Unless the person you spoke to knew nothing about the products they were supporting, which is possible but seems unlikely, then it was not their intention to do so. My guess would be that you provided incorrect or incomplete information to them, as you did to us. My point is that that is what happened and that has caused issues so you should acknowledge that and endeavour to avoid similar situations in the future. This issue could probably have been solved with Microsoft almost immediately with complete, accurate information and should have been here too.

    Regardless, you keep replying but you make no mention of whether you understand and have implemented the advice provided. Do you understand that you need to uninstall the Enterprise edition of VS and install the Community edition, regardless of the version? Have you done so? Did it solve the issue? If so then our work here is done and you can mark the thread Resolved. If not then what is the outstanding issue?

  16. #16
    Fanatic Member 2kaud's Avatar
    Join Date
    May 2014
    Location
    England
    Posts
    911

    Re: Licensing issues

    @PhotonBytes - Even if you use the free Community version of VS2019 or VS2022 you still have to register it with MS to be able to use after a certain length of time. Use Help/Register Visual Studio. You need a MS account.
    All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/

    C++23 Compiler: Microsoft VS2022 (17.6.5)

  17. #17
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by 2kaud View Post
    @PhotonBytes - Even if you use the free Community version of VS2019 or VS2022 you still have to register it with MS to be able to use after a certain length of time. Use Help/Register Visual Studio. You need a MS account.
    In the attachment that you can't see, it shows the OP has associated their Microsoft account with VS already. As that account is not associated with a license for Enterprise, it doesn't help them beyond the trial period, which has obviously now expired. Presumably they will be able to follow the same process in Community and not have the license expire.

  18. #18

    Thread Starter
    Junior Member
    Join Date
    Aug 2023
    Posts
    23

    Re: Licensing issues

    Installing now, thanks officers, I will be sure to drive on the right side of the street instead of the left as I'm used to in Australia!

  19. #19
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by 2kaud View Post
    [When trying to open the attachment, I get an error "Invalid Attachment specified. If you followed a valid link, please notify the administrator" ]
    Interestingly, I'm seeing the same error message now, although I could see the image yesterday.

  20. #20
    Super Moderator jmcilhinney's Avatar
    Join Date
    May 2005
    Location
    Sydney, Australia
    Posts
    109,966

    Re: Licensing issues

    Quote Originally Posted by PhotonBytes View Post
    Installing now, thanks officers, I will be sure to drive on the right side of the street instead of the left as I'm used to in Australia!
    Interesting that you're only now following the advice that was first provided 24 hours ago and multiple times since, but still maintaining, if a little tongue-in-cheek, that we're somehow being unreasonable. BTW, I'm Australian too so, if you start driving on the wrong side of the road, we might have a problem.

  21. #21
    Super Moderator Shaggy Hiker's Avatar
    Join Date
    Aug 2002
    Location
    Idaho
    Posts
    38,600

    Re: Licensing issues

    By the way, Community Edition IS Professional edition, just with a slightly different licensing setup. I use VS2022 Community Edition at home on two different computers. I frankly don't remember registering it the way 2kaud said would be necessary, but I also don't remember NOT registering it, so maybe I did.

    Enterprise edition adds...some things that I haven't ever seen the point in adding.
    My usual boring signature: Nothing

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width