Go to Post Reffing a FIRST event is unlike being an ump or a ref at any other event. Where else is a game invented each year and over 1000 teams play this game within 3 months of its birth? - Andy Baker [more]
Home
Go Back   Chief Delphi > Technical > Control System > FRC Control System
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
 
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #26   Spotlight this post!  
Unread 10-03-2015, 15:01
Crossle86's Avatar
Crossle86 Crossle86 is offline
Software Engineer
AKA: Richard Corn
FRC #4450 (Olympia Robotics Federation)
Team Role: Mentor
 
Join Date: Jan 2013
Rookie Year: 2013
Location: Olympia, WA.
Posts: 92
Crossle86 is an unknown quantity at this point
Re: Driver Station Update fails to install

Joe,
Just read your post. I am an experienced Windows developer and I also showed the DS program to another one of our mentors, who happens to be a Microsoft employee and a lead on the Windows team. Some observations:

1) I caused the create date of the DS program to change by copying it, which I did while trying to figure out why I was not getting the updated program when I renamed driverstation.exe to driver station.exe. Still no explanation for that but I am willing to drop it since I seem to have the updated program in place now.

2) Windows programs should always use a hard coded version or version based on the internal assignment of the 4 part windows version number, major.minor.build.fix or as I like to do major.minor.fix.build. If you use visual studio, all this can be managed automatically and your program can display the version embedded in the exe. If you are using LabView, then you have to manage the hard coded version yourself.

3) This version should be displayed in the application title bar though many developers leave off the build in the title bar. The title bar version and the version displayed by the app should not be of different forms.

4) Using file dates is not at all a good idea since the user can "change" the program version number.

5) Don't forget about the Driver user shell program not getting renamed. After a successful install of the update, the Driver user still runs the old program (hence the renaming I am doing). Note that I could have tweaked the registry to the correct program name, but I have our DS PCs set up to allow switching between the 2015 and 2014 DS programs as we still run last years robots quite a bit for demos and having the DS program name the same facilitates this switching. I know the 2015 is supposed to let you switch protocols, but this did seem to work when we first installed 2015 so we did it ourselves. And doing it ourselves allows us to switch out the custom display program we have for the upper part of the DS display.

Sorry if I am stating the obvious but I felt bound to mention all this due to the time I have spent on this version numbering issue.

Thanks for responding to my posts.
Reply With Quote
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 05:28.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi