Why Microsoft Disgusts Me Today
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Rick York wrote:
today's 15.9.9 update
Another one? We just had 15.9.8 last week. :wtf: I see the download for this update is "only" 1.4 Gb. I hate to think how anyone who doesn't have unlimited fibre broadband copes with this nonsense.
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
I have had grief with that site too. At one point they told me that the thing that I saw happen in Visual Studio 2017 was not happening... even though I had provided them with exact screenhots of the issue. Others had posted the same problem and confirmed. The issue was finally resolved just because it happened to be fixed in the next release anyways, but it was annoying.
Rick York wrote:
I am not sure I want to bother reporting the other issues I have run into.
That is the exact same effect it had on me. Since they just say, "oh, yeah, whatever..." and don't even bother to say, "ok, we'll look into this, it looks like something" it just ends up annoying you more really. I really don't like when these type of forums turn into that. StackOverflow/StackExchange sites often turn into this and so it teaches you to only be a "reader" and never a "reporter" which is really unfortunate. Especially in cases like yours - I read your reports and they contain very useful info that someone could take action on if they wanted to. But no. :sigh:
-
I have had grief with that site too. At one point they told me that the thing that I saw happen in Visual Studio 2017 was not happening... even though I had provided them with exact screenhots of the issue. Others had posted the same problem and confirmed. The issue was finally resolved just because it happened to be fixed in the next release anyways, but it was annoying.
Rick York wrote:
I am not sure I want to bother reporting the other issues I have run into.
That is the exact same effect it had on me. Since they just say, "oh, yeah, whatever..." and don't even bother to say, "ok, we'll look into this, it looks like something" it just ends up annoying you more really. I really don't like when these type of forums turn into that. StackOverflow/StackExchange sites often turn into this and so it teaches you to only be a "reader" and never a "reporter" which is really unfortunate. Especially in cases like yours - I read your reports and they contain very useful info that someone could take action on if they wanted to. But no. :sigh:
Those Microsoft employees were probably inspired by Monty Python :-\ Dead Parrot - YouTube[^]
-
I have had grief with that site too. At one point they told me that the thing that I saw happen in Visual Studio 2017 was not happening... even though I had provided them with exact screenhots of the issue. Others had posted the same problem and confirmed. The issue was finally resolved just because it happened to be fixed in the next release anyways, but it was annoying.
Rick York wrote:
I am not sure I want to bother reporting the other issues I have run into.
That is the exact same effect it had on me. Since they just say, "oh, yeah, whatever..." and don't even bother to say, "ok, we'll look into this, it looks like something" it just ends up annoying you more really. I really don't like when these type of forums turn into that. StackOverflow/StackExchange sites often turn into this and so it teaches you to only be a "reader" and never a "reporter" which is really unfortunate. Especially in cases like yours - I read your reports and they contain very useful info that someone could take action on if they wanted to. But no. :sigh:
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Honestly, I'm surprised the issue wasn't pawned off on the XBox App or Notepad developers; had an MSI issue with a "game" installer in the past and it was blamed on the XBox devs even though the game specifically targeted Windows having nothing to do with XBox anything. Feedback Hub & Insider programs need better filtration for isolation and then passed on rather than the inferred "the buck stops here" reporting services, front-end, desk jockey, cavalcade it persist to appear as. Had a few instances of error reporting sickness myself, so can relate unfortunately. Might explain why Microsoft was soliciting for "Insiders" previously as many have probably, like myself, decided to move on to other areas in our existence rather than awaiting canned answers or finger pointing placing blame on someone else's department. Blame != Professionalism (default) --there are exceptions to the rule, but generally (in the case of Windows error and feedback reporting) not too many.
I was unaware of that...
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Hi, I can explain why it's a Windows Platform issue. It's the OSG (Operating Systems Group) that determines which functions are exported from mincore. When I was working on the OneCore SKU now called "Windows Core OS" it would take several weeks/months and a vetting process to get any functions added to mincore. I'd recommend following up and posting on the feedback hub. Maybe you can have @Richard-MacCutchan also give some feedback. [He complained about the same issue](https://www.codeproject.com/Lounge.aspx?msg=5541014#xx5541014xx). I believe they are using a weighting algorithm based on how many people complain about the same thing over at feedback hub. Best Wishes, -David Delaune
-
Hi, I can explain why it's a Windows Platform issue. It's the OSG (Operating Systems Group) that determines which functions are exported from mincore. When I was working on the OneCore SKU now called "Windows Core OS" it would take several weeks/months and a vetting process to get any functions added to mincore. I'd recommend following up and posting on the feedback hub. Maybe you can have @Richard-MacCutchan also give some feedback. [He complained about the same issue](https://www.codeproject.com/Lounge.aspx?msg=5541014#xx5541014xx). I believe they are using a weighting algorithm based on how many people complain about the same thing over at feedback hub. Best Wishes, -David Delaune
I can understand why that would be the case. I don't think that's really the problem though. I haven't tracked down the various DLLs and checked their exports to see where the functions actually are but the fact is I shouldn't have to. The documents say link with mincore.lib so I do that and the app links. However, when it runs it can't find the DLL it is supposed to import the functions from as I have explained. This means the linking process is messed up and I don't feel like doing their work to sort it out for them. It seems to me they should be able to just change where the functions are imported from as part of linking with that library because the missing DLL is explicitly imported by the app.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
I can understand why that would be the case. I don't think that's really the problem though. I haven't tracked down the various DLLs and checked their exports to see where the functions actually are but the fact is I shouldn't have to. The documents say link with mincore.lib so I do that and the app links. However, when it runs it can't find the DLL it is supposed to import the functions from as I have explained. This means the linking process is messed up and I don't feel like doing their work to sort it out for them. It seems to me they should be able to just change where the functions are imported from as part of linking with that library because the missing DLL is explicitly imported by the app.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Rick York wrote:
It seems to me they should be able to just change where the functions are imported from as part of linking with that library because the missing DLL is explicitly imported by the app.
No, the compiler group consumes mincore.lib generated by the operating system build. Not the other way around. I can see why this might be confusing to someone on the outside. You should just post something regarding the problem onto the feedback hub so the correct team gets visibility into your issue. Best Wishes, -David Delaune
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
They're busy fixing more important issues[^].
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Tell them it's preventing you from seeing one of the new icons. They'll fix it right away.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Tell them it's preventing you from seeing one of the new icons. They'll fix it right away.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
Dude, I've been waiting for a couple of bugs to be fixed in FORMAT and FDISK since, oh, let's see now, .... ah, 1991! Still waiting.
Asking questions is a skill CodeProject Forum Guidelines Google: C# How to debug code Seriously, go read these articles.
Dave Kreskowiak -
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
beuz u can
The best way to improve Windows is run it on a Mac. The best way to bring a Mac to its knees is to run Windows on it. ~ my brother Jeff
-
Last October I submitted a bug report [^] and made several comments elaborating on the problem. It has to do with the FileVersionInfo family of API functions and how the their build process is broken because programs are linked to the wrong libraries which don't contain the relevant functions. There have been several updates since then and I install them all and the problem hasn't been fixed yet. I had actually written this off as yet another Microsoft-ism but I noticed they finally replied to my report : "Thank you for your feedback. We have determined that this issue belongs to the Windows platform. Please provide feedback using Windows 10 feedback hub store app. For more information, see https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app" What the ...? this is most definitely NOT a platform problem. It is a problem with their linker configuration because VS207 links my programs with the wrong libraries which are either not present or do not contain those functions. There is no work-around available other than not using those functions so I have to implement similar functionality myself in a different way. :rolleyes: This is really getting tiresome. I am not sure I want to bother reporting the other issues I have run into. One is very annoying because it requires that we install the redistributable package. I wanted to use static linking but that is not an option. -edit- because of this problem, I can't use the statically linked version. :wtf: /edit BTW - the problem is still present in today's 15.9.9 update. I tried it and that attempt inspired this rant.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
so u are telling that they did not fix dll hell ...
Caveat Emptor. "Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
They sort of did fix that but they are finding different ways to break things. Another thing - when I link with static libraries then my apps can't load resources from the libraries so several of the built-in controls won't work. The hits just keep on coming. The most annoying thing is the fingers are pointed at someone else and there is no way (I have found) to inform the target of those fingers. This means the likelihood of the issues being fixed is minimal.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
