More for the C++ developers, but still relevant:
More for the C++ developers, but still relevant:
When installing RAD Studio #10Seattle Update 1, make sure you don't accidentally uninstall the Windows SDK at the end. When it is executed, if you already installed it, the only option will be remove. And it does remove a few extra files than it should, so it will mess up with the C++ installation
When installing RAD Studio #10Seattle Update 1, make sure you don't accidentally uninstall the Windows SDK at the end. When it is executed, if you already installed it, the only option will be remove. And it does remove a few extra files than it should, so it will mess up with the C++ installation
In hindsight, this should have been provided in the description upon downloading. Just my 2-cents
ReplyDeleteAlso in the event the Windows 10 SDK was removed how would a person reinstall it and how would a person repaired the C++ installation ? Wait for Update 2 ?
ReplyDeleteRichard Baroniunas It probably happened just recently...
ReplyDeleteUwe Raabe I understand but that is no excuse for missing something like this during the testing.
ReplyDeleteIt seems there is a bug in Microsoft installer than we in fact missed... Still doing some investigation. yes, we should have found it, but it is NOT our installer.
ReplyDeleteMarco Cantù Based on what you wrote that Windows 10 SDK is removed and there is a possibility that the C++ installation will be messed up then in my world that either the QA team or the supervisor would be demoted or fired.
ReplyDeleteThis is after the statements that the update 1 was tested and care was put into it that was the reason behind the delays. Sorry but for the amount of money spent on the product I expect better.
Let me clarify: the error happens if a developer runs the Windows SDK installer (a second time, after he originally installed it with 10 Seattle) and doesn't notice that the only valid option is "Remove" and pressing OK ends up removing the feature rather than installing it. This is itself should cause no harm. However, it seems from some reports that this uninstall ends up deleting some extra files. It seems meaning we still have to do some extra testing to make sure which exact step caused the file to disappear.
ReplyDeleteNow all of this is 100% a Microsoft installer we only invoke. I agree we should have done testing in that scenario (rather than canceling the "SDK removal", which is probably what our testers did -- or install on a new system) and find out that some code won't compile any more.
We could have find out and warned customers, for sure. I was the first to alert people of this. This has nothing to do with testing the update 1. If you just install the update 1, this issue does not happen. It is installing the SDK from Microsoft that has unexpected side effects we are investigating.
When running a MSI installer of the same version, it will go into maintenance mode to modify repair or remove. In this case it was remove. I did remove because I was assuming the update installer was going to reinstall. It didn't. I don't dev in C++ so probably won't be hindered.
ReplyDeleteTechnically, the Windows SDK is not needed to build any type of RAD Studio projects, including C++. It is a requirement from Microsoft. That's why we kind of overlooked it. Why exactly removing it can cause trouble is not really known at this point. We are investigating the issue.
ReplyDeleteRichard Baroniunas That's extraordinarily harsh. Firing / demoting someone for missing one problem in software that isn't even made by Embarcadero?
ReplyDeleteIt's pretty hard to get everything right, but a bug like this isn't even a severe problem.
David Millington Just to let you know that in the finance companies such as any major banks or firms such as Goldman Sachs, a mistake is handled with the following (write-up on performance which could affect your next raise; a person could be demoted to doing simple tasks until they prove themselves again; a person could be fired if the severity lost the company money).
ReplyDeleteAn incident where a programmer in a major bank, had a minor bug that affected the routing of SWIFT payments to become cancelled payments, the small bug and careless QA creating a set back for the major bank not to handle over seas transactions for 2 business days and thus is a huge loss in revenue.
That being said, the QA department was written up on missing the bug and the programmer was led out by a security team.
The problem that was created in this thread is a failure on someone who was QAing the installation and at this stage should not have happened at all. This is regardless whether the SDK is needed or not but reflects during the transition from EMB to Idera that a sloppy release is not good.
I may be the only one who expects better.
I don't think a problem where a Microsoft-supplied installer might uninstall is anywhere near the same level as a major bank being unable to handle transactions.
ReplyDeleteI just wanted to point out your comment was extraordinarily harsh. I don't think you've rebutted that, and I think your expectations are high (which is good) but that doesn't seem so important for an installation issue that is, frankly, minor, and if it occurs is easily fixed. I don't really think calling for an employee to be fired because a third-party product has a potential problem is in any way appropriate to the severity of the issue.
Richard Baroniunas I honestly think you are overreacting for an issues that for now (to my knowledge) has affected 1 developer, who was able to get back on track quickly.
ReplyDeleteDavid Millington Let's agree we see things differently. To myself Quality assurance is top key for any type of software release.
ReplyDeleteIf the Windows 10 SDK was removed on a machine that was using it and my employees lost man time figuring out what happened it would cost me money overall, do you agree on that ?
It is OK to say that this is a minor problem but in the big picture when I purchase any software (including yours) I do expect that it was fully tested prior to software release.
I can understand Alpha or Beta releases with problems but something like this from a major company does create issues on trust.
Windows 10 SDK is removed if the developers clicks OK under the Windows SDK installer saying "Remove", the fact it is triggered with that option is not ideal. Now while a QA person could have told us "wait, this is confusing" it is not a bug in the technical sense. Consider also that strictly speaking the Windows SDK is not needed but RAD Studio.
ReplyDeleteNow if under some circumstances the Windows SDK uninstaller misbehaves, which we are still not 100% sure, this is hardly an issue for an Embarcadero QA person... much so for a Microsoft one!
Marco Cantù David Millington Sounds good to me, let's close this thread out.
ReplyDelete