This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
The visual studio 2022 community EULA clearly indicates which runtime dlls are distributable. However, there is no specific guidance with regard to statically linking to the CRT. Since debug dlls are not redistributable it seems logical that an application that is statically linked to the debug version of the CRT should not be distributed. Similarly, it seems logical that an application that is statically linked to the release version of the CRT should be freely distributable.
Some have asserted that the license agreement for the community edition precludes distributing any application that is statically linked to the CRT. Is this a correct interpretation over the agreement? Can Microsoft please provide an authoritative response to this question in this forum.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 12%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
I vaguely remember that older versions of the free VS editions would not allow you to statically link the CRT, but I don't know if that's still the case.
Can you point out where in the community edition licence it mentions this?
There's nothing that I can see in the Community 2022 EULA with respect to static linking. That's why I posted the question.
Ah, I couldn't see anything either :)
So, can the "some have asserted" point us to anything?
Before I challenged the assertion I was hoping to get an authoritative response from MS. That would avoid any debates over license interpretation. If the assertion is correct then there's no need to challenge it. If it is incorrect and the authoritative answer is in hand then making the correction is helpful and informative.
Since the Community version can be used for commercial purposes by those who meet the terms of the license it seems unreasonable to me that there would be any restrictions on static linking with the release versions of the libraries. But what is reasonable and what a loosely worded license agreement require may not be the same. :)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 78%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
Hi @RLWA32 ,
Welcome to Microsoft Q&A forum. Since you want to get an authoritative response from Microsoft, I suggest you call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M.(Pacific Time) to speak directly to a Microsoft licensing specialist and better confirm this.
Besides, I also didn’t see the related guidance with regard to statically linking to the CRT. I have reported to improve the official documents you mentioned.
Regards,
Tianyu
This phone number is answered by a bot that gives no clear path to contacting a licensing specialist for Visual Studio Community.
Provide specific instructions on the keypad responses that are needed to get in contact with a human being that can answer a licensing question.
Update --
I tried again. This time the bot told me that support had moved online and hung up on me.
THIS PROCESS IS ABSOLUTELY USELESS!
Update 2 --
Two more attempts to speak with a licensing specialist met with failure as the automated system disconnected my calls.
Update 3 --
More calls. More disconnections. Is 800-426-9400 really a phone number for a licensing specialist?
Hi @RLWA32 ,
This phone number is valid. You may need to confirm following two aspects:
If you still fail to connect to above phone number, you can try this: Here lists the global customer service phone numbers.
Regards,
Tianyu
You misunderstand. The call connects and an automated attendant does one of two things -
In every case the automated attendant is incapable of connecting the caller to a human being that is a licensing specialist.
This seems to be a futile process. Kindly escalate this problem to an appropriate contact within Microsoft.
Hi @RLWA32 ,
I have reported this license issue, here’s the thread link. Please kindly follow up that thread.
Besides, I would suggest you try to create a new support case for better help(if you have related VS subscriptions) > open this Get Help link > scroll down and click Create a new support case button > choose Licensing terms > select "What are the subscription licensing terms and conditions" and click "Online request".
Regards,
Tianyu
Thank you for following-up. Even though I do not have a Visual Studio subscription and am inquiring about the Community edition I followed your instructions and opened an Online support case for this licensing question.
I will share Microsoft's response to this licensing question when it is received. Hopefully, the response will address the question and not dismiss the issue due to the absence of a subscription.
Update -
In addition to the DeveloperCommunity issue status being changed to "Under Investigation" the initial response from MS to the Support Case that was opened is "I would like to inform you that your concern has been escalated to our Microsoft Visual Studio Subscriptions Support Team."
@Tianyu Sun-MSFT Well, opening a support case with Visual Studio Subscriptions accomplished nothing. They passed the buck back to me with instructions to start over by visiting https://visualstudio.microsoft.com/vs/support/. I can't say that I'm surprised.
I suggest you follow up at Developer Community where the issue you opened was marked as "Under Investigation" a week ago. Hopefully they will be more helpful. Its disappointing that getting an answer to such a simple question has proven to be so difficult.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 39%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBV%3C/text%3E%3C/svg%3E)
I remember a long time ago that static linking as a concept was being up for discussion. If the community edition. You asked for a formal Microsoft reply so mine is not going to be that answer but if the community edition does allow you to statically link, and if the EULA doesn't specifically say anything about it, I would conclude that for release builds there shouldn't be a problem
I share your opinion. But I'd like an authoritative answer to my question.
From a legal pov that makes sense and I agree with you that if there is uncertainty, it's always better to ask for permission.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 87%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
I agree with the opinons expressed here. Are you able to statically link in the community edition? (I cannot seem to get this to work.)
@Tom Sabourin I have not encountered any problems statically linking with the CRT. I suggest that you ask a new question in which you provide pertinent details if you are unable to link statically with the CRT.