Danny has posted some information on our analysis of the problems that folks are having with the .NET 1.1 SP1 update that was just released a few weeks ago. Now before you get your knickers in knot, we will at least release an interim patch to get folks back on track. However it will take some time for us to fully regress any changes before releasing an “official” update. The problem is, as Danny stated, we simply don't know at this point what the correct fix should be. The worst thing we could do at this point is to bow to all that borland.public.delphi.non-technical pressure and rush a fix out the door. We need to step back, take a deep breath, and attack the problem calmly. We certainly don't want to make the situation worse. I recommend to all those folks that seem to be using this as an excuse to break out the flame-throwers, to take that same tactic. Slow down and take a deep breath. There is truth in the old adage, “haste makes waste.”
Your link to Danny is invalid. ;o)
ReplyDeletePressure in borland.public.delphi.non-technical is meant to try to make Borland warn customers instead of waiting until they have this problem and check the newsgroups only to find out it is know for several weeks. Please warn customers. I am in trouble, but don't let other come into the same position, please.
ReplyDeleteAllen: Agreed. Please take your time and fix it right.
ReplyDelete-d
Rick: That is only one reason for all the hub-bub. There are plenty of other folks who seem to delite in blowing things totally out of proportion. Not that this isn't a big problem, it is, but there needs to be some level of perspective. We are focused on solving the problem. I'll let the folks who control the "official" channels of communication make the call about when and what to warn about. Besides, this is precisely why we have these blogs. Many times the "official" channels are clogged with red-tape but these "unofficial" channels are not.
ReplyDeleteAllen: I was dissappointed at first. Installed the update at home and after the weekend at work (without using Delphi that weekend at home). Unfortunately I missed the ng posts that something was wrong. I hope others will be more careful and check ng's first (or try one PC first).
ReplyDeleteI am very satisfied with the way you all handle the problem itself. I think it is best to get a good solution instead of a quick one. Problem couldn't arrive at more terrible moment I guess.
Allen: "There are plenty of other folks who seem to delite in blowing things totally out of proportion."
ReplyDeleteAre you serious? They call those people "customers that use software!" :) It amazes me how life has changed:
Used to be:
"I need to find some food and shelter or I am going to die."
Now:
"Every 100th time I fire up your app on my WinME Pentium 90 w/ 32 megs of ram, I get an error. You said two days ago you were working on it. Where is the fix?"
Just thought you could use a laugh! The paced, methodical fix is always the best. Take the time to make sure it is right.
Of course fix it right... time on the other hand is something that nobody in development has an abundance of... Just two thoughts:
ReplyDelete#1: Curious why Borland would not have forseen changes to .NET coming??? It would seem to me that in this world of security consious IT professionals we would not have taken patch management into consideration... What happens with the next update and I'm in the midst of development like this time? (my development team is down right now until I resolve this and it's the time that it takes to fix this that is costing me, not to mention lost productivity of the developers). Can I submit an expense request to Borland Corporate somewhere to cover my cost??? :(
#2 I hope someone is going to stay at home to fix this issue ASAP... or is everyone trotting off to the Borland Conference :)... Let's go parade Delphi 9 while Delphi 8 is stuck in the mud!
Stew:
ReplyDeleteThe fact of the matter is that we were simply blind-sided by the SP1 release. In fact, when we were contacted by MS about its "emminent" release, we told this person that it was already out and that we're getting reports. This MS contact, was shocked that it was *already* out!
As far as BorCon, that's over. In fact by the time you posted your message, it had been over for nearly a week, so I fail to see the relevance.
The post regarding the BorCon was tongue in cheek... The problem with the .NET patch existed since well before the conference... I was just curious if it was important enough to have technicians hang back and fix the problem or not...
ReplyDeleteYour reply to my post, and that fact that you didn't see the humor in it, besides the little smiley face, indicates that the problem is more serious than insiders are letting on...
Thanks for the insight!
Stewart:
ReplyDeleteWe never said the problem wasn't serious or a cause for concern. Quite the opposite. As soon as we were aware of the issues, we immediately recommended that folks refrain from installing the SP until we've had the chance to evaluate the problems and come up with a plan. No matter how well you plan, there is going to be those times where something unforseen is going to bite you. I know this doesn't help those that had already installed the SP, but we're only able to work with the data we have.
I think we have to wait for Borland to come up with an solution but for now is there a way to roll back the system?
ReplyDeleteI have restored a restore point but this is not working. Uninstall the .Net framework and the SDK and reinstall it again is also not working. Uninstall and reinstall Delphi 8 not working.
Any ideas how to solve this?
It's now well over a month since these early posts were going on. Has Borland come out with any response to this problem yet? I do notice that D9 is being paraded and get a gut feeling that D8 will be forgotten about now. What a waste of money....
ReplyDeletewell ...
ReplyDeleteI'm not a native english speaker, so I need a clear answer, please - I couldn't find a work-around myself until the moment.
I bought for my small company 10 delphi8 pro licenses and I'm not laughing about the issue due to the general update 2 ... there's noway for us to "avoid" .net fw 1.1. sp1!
Is there a traceable/reproducible work-around to repair delphi8 for .net fw WITH sp1 AND the general update 2?
I really thank You for a satisfying answer!
Sincerly, Nepomuk
I forgot this:
ReplyDeleteA solution for a "virgin" newly installed environment would match my needs ;) - it is not obligatory required to patch an installed environment.
Thank You, Nepomuk
I have just purchased Infragistics Netadvantage 2004 Vol 3 to use in my Delphi 8 Pro environment and am having some problems that I hope someone can help me with.
ReplyDeleteEverytime I add one of the components to a webform, or do some mods in one of my classes I cannot recompile. I get the following error message
"[Warning] JobTracker.dpr(47): File not found: 'Admin\bin\JobTracker.dll.licenses'"
Sure, I know if I copy the licenses file to the relavent folder the error goes away, but then later it wants it in some other folder, then another, then another. I am going to end up with the licenses file all over my HDD.
My current solution is to go into the project source and remove the offending line. I then have to close and re-open the project before compiling as Delphi8 raises an exception if I try to compile straight after removing the line. This is tedious to say the least... Never mind Delphi removing markup from my ASPX page when it feels like it, telling me to recompile base packages I have created even when I do recompile etc...
I too have the feeling that Borland have put all their effort into Delphi 2005 and left us D8 users our in the cold. It appears the attitude of Borland is "stuff you - you want D8 fixed - upgrade to 2005". There is no news or ideas anywhere on an Update 3 that could resolve some of the D8 issues.
I pushed my IT Manager to purchase 4 copies of D8 Pro and am regretting it. I think VS.NET may have been the way forward. Delphi's days appear about over. If Borland want to push us users aside that have used their product for years, then we can do it back. Borland needs us more than we need them!