This is the sort of thing that drives me completely nuts
Updated: 21 May 2010 | 5 comments
When I think about how simple it would be to trap this kind of error..
I made a simple mistake, i.e. not including the last quote mark on a condition. Why, on God's earth, the WPS compiler cannot trap that before it goes merrily on its way to building what will inevitably be a non-functioning MSI (bails, with error 2717)? HOW HARD CAN IT BE?!?!?
I realise all too well that my rant will result in zero action but, if anyone were to wonder why people switch tools, this sort of nonsense provides as clear a pointer as any.
discussion Filed Under:
Comments
Are you not stretching this
Are you not stretching this to the limit now Ian?
Just of interest, how did you add the condition; table editing, condition builder and if so did you use the syntax checker (or what it's called)?
Cheers!
syntax checking
considering they already have the logic for the syntax checking built into the macro editor I guess you are right.
log a feature request, in the past I have noticed they never work but its worth a shot haha
Kim, I added it when editing
Kim, I added it when editing a CA in 'MSI Script' view. I didn't use the syntax checker, as the condition was simply REMOVE~="ALL". Besides, all the syntax checker would do is tell me that it was wrong, not tell me WHY.
And what do you mean "stretching this to the limit." Stretching what?
>log a feature request
He's a joker, that John, isn't he? LOL
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
We all make mistakes
Jeez Ian,
Don't get so worked up about a simple typo - I'm sure it did not take you long to spot the error.
At this rate you're going to end up on a slab, and then who will be left to extract the urine from those too lazy to look on Google...??
If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.
>I'm sure it did not take you
>I'm sure it did not take you long to spot the error
That was kind of the point. I didn't spot it until I'd compiled the MSI, re-added it to a GPO, reset a VM to a snapshot, logged in with my user-level test account, cursed because the deployment failed and finally spotted the error in the log. Only an hour down the tubes...
>At this rate you're going to end up on a slab
That is about as likely as getting a WPS feature request from the 'request' stage into the 'release' stage.
Don't know why 'x' happened? Want to know why 'y' happened? Use ProcMon and it will tell you.
Think about using http://www.google.com before posting.
Would you like to reply?
Login or Register to post your comment.