Breaking changes in VS

[ic2]

Just read the message

"Unfortunately there are some breaking changes in this build that may result in Visual Studio locking up when you build a XSharp project. That is not good. We have heard about other project systems with similar effects. The problems seem to be related to changes in MsBuild."

This is typically Microsoft.

Oh, wait, I just read you strongly disagree with that because the first builds where smoothly with Visual Studio.

Pure beginners luck.

I even know people who can't remember having problems with Microsoft software. It's just a few people, but they actually exist. Or they have severe memory problems, which is more likely. This year I spent already nearly 2 full work weeks on software installation and following problem solving and 90% is trying to find out how I get some Microsoft product working. My laptop, which doesn't actually doesn't show many problems except that I have to reset it 50% of the times to get a network connection was impossible to update to Windows Creators version. I tried everything I could find and on answers.microsoft.com I asked for the meaning of 2 specific error codes which were logged. These were undocumented on https://docs.microsoft.com/en-us/window ... ade-errors so I hope someone could tell me the meaning so I could probably find the cause. Microsoft moderators gave some unusable reply but nothing about the error codes. I finally decided to do a clean install. After I have solved all the problems and installed all the software I have one advantage of the Creators Update: I can postpone the next update for a full year. Every new Microsoft version gives more problems and is slower or takes more steps to do something than the previous. Every other update I run works smoothly: X#, Firefox, Filezilla, you name it, it works or problems are extremely rare.

Even after I decided to update Office 2016, completely the default way, (no idea why I did it, there was nothing I needed) this was happened after the next startup:

Office2016Opstart.png (93.65 KiB) Viewed 285 times

In Program and features you can start for a quick repair. This worked, but the next time, same problem. Tried twice. Tried the not quick repair. That was actually a complete reinstall (including entering my product key) and re-entering changed settings. And then it worked again. But I will never update this piece of shit ever again. How difficult can it be, delivering a working update?

Same goes for Visual Studio 2017. Most of the installation could not be finished. My Windows Universal Apps didn't work anymore in VS 2015. Using one of my 10 multiple 100 $ incidents, and the help of a very good support lady (there are some good people working for Microsoft) , who deleted all kind of directories manually and had to take ownership of others, I had a more or less working VS 2017 but 2015 remained crippled. After deinstalling VS 2017 everything worked again in VS 2015 and that's how I keep it. I don't even dare to install the Professional Version from Action Pack - no doubt it breaks something.

So I wish you all luck with solving the problem and I understand that you can not say, dear user, please use VS 2015 and stay away from everything newer. But it would be a wise advice!

[wriedmann]

Hi Dick,

please don't see it so bad!

The Windows systems have become so complex, and also Visual Studio is a very complex and large software package, so errors are absolutely normal.

I'm working also much with Linux (at least on the server side), and I can assure that I had several very discutable design decisions also in the Debian group, the Samba team and other large projects - changes that broke the compatibility to older installations and gave me severe problems.

Unfortunately, we programmers are humans and not only make errors in programming, but sometime take also bad decisions.

Wolfgang

P.S. I'm using Office 2010 on my machine - not because I don't like the newer versions, but because Access 2010 is the last version that can deal with the MDB files I need in a project. And yes, I have not installed VS 2017 because I don't need it.

[robert]

Dick,

It must be nice to live in a world where everything is white or black. Like an old western movie where you could immediately spot the good guys on the color of their hats.
Unfortunately reality is different.
The good news is that we were able to work around the problem: we were (ab)using something in Visual Studio for something that was not originally planned.

Let me give an explanation in XBase terms:
Assume you want to put a text control on a form. This control must be used to enter dates. To verify that the user enters a correct date you send the contents of the control to the CtoD() function. If the result is not an empty date then you assume the date is correct. After all: the specs of the CtoD function tell you it returns "The date value that corresponds to the numbers specified in <cDate>. If <cDate> is not a valid date, CToD() returns a NULL_DATE."

Now a new developer comes and changes something in the CtoD function. He is very clever and reasons that when someone sends in a date string where the month > 12 and the day <= 12 then they most likely swapped the day and month (i.o.w. were using an incorrect date format). So he decides that in cases like that he should swap the day and month values and returns a valid date where the original function would return an empty date.

And of course this new "enhanced" function breaks your validation code.

Now the question is: who made the mistake here? Who is to blame?

Robert

[ic2]

Hello Wolfgang, Robert,

The Windows system is complex indeed, but my main problem here is that nobody can answer on even the meaning of the error codes. So installation problems remain unsolvable.

And almost every Microsoft product fails. What about the Office problem? It's a 100% standard installation. I've installed Office 2016 only because Office 2003 sometimes fails reading docx files. I prefer Office 2003 because it's way faster, take less steps (1 instead of 3 on saving a file for example) and only Excel 2003 can save as a .dbf file. But even a simple update of Office 2016 finally required a complete reinstall.

Microsoft has large resources. Instead of using these to make their products rock solid they use it to turn W10 in spyware and complicate almost every action. So yes Robert, unfortunately the software world is pretty black and white as every Microsoft product fails somehow (apart from Windows, Windows Server, Office I can already write a chapter about Azure too)and most of the other software programs I use have major problems. I don't know anything about Linux except that I know a few ex Windows users who went to Linux and tell me that it's far more stable.

Anyhow, Robert, good that you found the cause of the X#/VS 2017 problem and that maybe Microsoft is not to blame for it.

[NickFriend]

Oh dear Dick!

I'm sure you have all these problems and they're not just the result of bad dreams but just for the sake of balance,and for anyone maybe beginning the move to .Net and wondering about Visual Studio after seeing your horror stories....

Like many others I've used VO since pre-release days, and continue to use it on a nearly daily basis for maintenance of old apps. But about 5 or 6 years ago I started the transition to .Net with C# and VS. Nowadays I hate the time I have to spend in VO, because of the limited functionality of the VO environment, and because of the limitations of the language compared to C# (and now X#).

Visual Studio is simply superb... productive, easy to use and utterly reliable. Now, I started with VS2010 (I think), then 2012, 2013. I didn't like 2015, it seemed very slow, so only ever handled one project with that. Now that 2017 has come out I find it comparable in speed again to 2013, so I've moved across to 2017.

Windows, no problems. I have automatic updates switched on and just let it do it's thing... no problems.

Azure, great. There's so much functionality that it can be confusing, but I keep it simple with a series of virtual servers running the server ends of our WCF-based applications, and it just works 100% of the time, good access speed, etc.

So I'm not saying you don't have all sorts of problems, but I think you're the exception, not the rule! One point, if you switch off updates and don't update Windows or other components for a couple of years, and then try to update all at once, then frankly of course you're going to have problems. With the best will in the world (and as someone else pointed out these products are now immensely complex) it's very difficult to reliably update software from any point in the past to a new fixed point. I hate it when our users don't update for several months because it makes the updating process so much more complex - we force them to do it multi-step going through each pending upgrade to make sure everything is correctly updated - whereas those users who simply accept the automatic update are always synchronized with us.

Anyway, I hope you solve all your myriad problems.

Nick

[wriedmann]

Hi Dick,

The Windows system is complex indeed, but my main problem here is that nobody can answer on even the meaning of the error codes. So installation problems remain unsolvable.

I had a discussion about support yesterday with my wife (she is also my partner in business, and where I'm responsible for desktop development, she is responsible for the web development in our small company).

The main problem about support is that you would need the best people in the support team because only very smart people can give a good support. But good people is not able to remain in the support team as the work is very frustrating, and most of the questions are very stupid and repeated over and over.

It is enough to see the questions that are posted in the various VO NGs: some of them are very stupid, and only a genius with some clairvoyant capabilities could answer them.

And returning to Microsoft: I have my doubts they have anyone that understands the entire system.... I have seen a few numbers of the Windows source code (now entirely in GIT as the Linux kernel): more than 300 GB of code with 3,5 millions of code files. The team has about 4.000 people, and every day about 2.500 pull requests.

Your Office installtion issue probably was somewhat related with your Windows installation, so it may be nearly impossible to identify the causes.

Regarding Linux: yes, it is rock solid - I have servers with years of uptime, but sometimes they make also mistakes or break the compatibility. The latest was that the Debian team has replaced MySQL by MariaDB, breaking my databases at the upgrade.

Wolfgang

[NickFriend]

The main problem about support is that you would need the best people in the support team because only very smart people can give a good support. But good people is not able to remain in the support team as the work is very frustrating, and most of the questions are very stupid and repeated over and over.

Sigh... this is so true!

[FFF]

Wolfgang,
Your answer misses Dick's point: there should be a complete list of error codes available on the net. There have to be procedures in place which prevent the definition of a "new" code without solid explanation of meaning and entry in this (one) database.

BTW, 3.5GB of source for an OS? I shudder seeing that a simple OS install procuces over 100k files. Time for a big step back, and a new start... And no, i don't mean "*nix" - which is even morre of a dinosaur...

[wriedmann]

Hi Karl,

Your answer misses Dick's point: there should be a complete list of error codes available on the net. There have to be procedures in place which prevent the definition of a "new" code without solid explanation of meaning and entry in this (one) database.

This could be difficult with such an enormous project....

BTW, 3.5GB of source for an OS? I shudder seeing that a simple OS install procuces over 100k files. Time for a big step back, and a new start... And no, i don't mean "*nix" - which is even morre of a dinosaur...

the sources are 300 GB, the number of files is 3.5 millions.

I don't think someone on this world can afford it to rewrite a complete operating system like Windows or Linux. Even Apple took the BSD kernel for their iOS, and Google Linux for Android.
I don't think that all our code would be run on a completely rewritten operating system.

The sources of the actual Windows OS started with Windows NT 3 by Dave Cutler in the year 1988, and were largely inspired by DEC VMS, also developed by Dave Cutler. This OS became stable only with NT 4.0 in 1996. The GUI was mostly taken over from Windows 95.... and there was people saying that the TCP-IP network stack was copied over from FreeBSD.

For some time, the best experts of Windows networking were not working for Microsoft, but in the Samba team - they reverse engineered the protocol and knew it better than the MS people that had the sources, but no knowledge anymore.

Wolfgang

[ic2]

Nowadays I hate the time I have to spend in VO, because of the limited functionality of the VO environment, and because of the limitations of the language compared to C# (and now X#).

Visual Studio is simply superb... productive, easy to use and utterly reliable. Now, I started with VS2010 (I think), then 2012, 2013. I didn't like 2015, it seemed very slow, so only ever handled one project with that. Now that 2017 has come out I find it comparable in speed again to 2013, so I've moved across to 2017.

Nick

About the language I fully agree with you of course. That's why we follow or use X#. However, the VO environment IMO is vastly superior to VS in almost every respect. Simple samples: the ability to sort on last changed entities, to edit any number of entities and the order you want instead of the whole .cs/.prg at once, a very easy way (icons) to split a screen horizontal/vertical or both and unsplit it again which is impossible in VS and for the only working split I need to help file every time so I don't even use it anymore. Commenting and uncommenting in VO is Ctrl B and in VS you comment with something like Ctrl K Ctrl U Alt P and uncomment with Shift G Ctrl Q Alt D - I can give many more samples where objectively VS is light years behind VO. I do not doubt you found advantages, I certainly have found some too (Immediate Window can do more than VO's Ctrl X and it's possible to see the value of all elements of e.g. a list while VO stops at 256 elements, and the Peek Definition) but everything together I hate every second I work with VS.

What I found very interesting to read is that you consider VS 2015 slower than earlier versions. In my idea nothing much changed in speed and VS 2015 introduced the Peek Definition so I found it slightly better than earlier versions. I really expected much of VS 2017 but found it considerably slower than 2015, despite Microsoft's promise that it would be so much faster. There are many reports from people complaining about the same problem but maybe they have solved that problem somehow.

So I'm not saying you don't have all sorts of problems, but I think you're the exception, not the rule! One point, if you switch off updates and don't update Windows or other components for a couple of years, and then try to update all at once, then frankly of course you're going to have problems.

With the best will in the world (and as someone else pointed out these products are now immensely complex) it's very difficult to reliably update software from any point in the past to a new fixed point.

Nick

Then the internet is full of exceptions apparently. You can quickly check that : I posted my VS 2017 problems in https://developercommunity.visualstudio ... ous-s.html

It immediately got 130 people following. If I looked up on the keywords Visual Studio 2017 slow (or installation problems etc) I could find multiple similar postings daily, each with 100-300 followers, for weeks. So my estimate is that 1000's of VS 2017 users were having problems including those who did not react in these website. Which is a fairly high number. I think you can find 10.000's of exceptions with W10 problems which can easily multiplied by 100 at least meaning millions of people having one or more serious W10 problems.

And I do not postpone updating for years. I update my Windows security patches every 6-12 weeks which should be more than covered by the integrated KB updates containing all single previous ones - including the repairs of failing single updates in that period. And for Office - I don't see why such a program with a couple of pages of slightly adapted features should be updated in 8 pieces instead of 1 (my last update was from November 2016) unless its design is even worse than I already thought. I don't have these problems with our software either and further: in my opinion you have spend so much time (also compared to what we did) in writing perfectly "by the rule" designed software that I could hardly imagine that your software would fail when being updated delayed.