You can build projects of choice even if you have multiple in the current workspace by right clicking the project you want to build/perform XXXX on in the Solution Explorer and then choosing the appropriate action.
You don't need Microsoft do implement this for you; you can do it manually yourself. You can add/edit existing configurations (e.g. Debug, Release, or custom-named) and then set custom Preprocessor definitions under the C/C++ tab on the properties.
That'd allow you to add a Preprocessor definition like _WINLIB when the configuration is for a static library (and you can decide when it is/isn't by setting the Preprocessor for the Configuration of your choice).
This is an incredibly bad idea and I'll hint as to why... security. Unless Microsoft were to do serious work with it (which would be a bad idea since they have more important things to focus on), it would be a security risk to promote more to be using VB6. Furthermore, if Microsoft did do serious work with it to make it more secure, it'd no longer be "VB6".
Anyone who seriously thinks bringing back VB6 is a good idea for development of something an end-user is going to use probably should not be developing for end-users in the first place. This is 2018, not 2000.
That is like me saying "Bring back Windows XP which won't have all the performance and security improvements internally which Windows 10 has".
27 votesDontBringBackVB6 supported this idea ·