|
( I hope my description is clear enough)
We allow installing major versions of our application in parallel (for example, 1.0, 2.0, 3.0)
For minor versions releases, we patch the current version (for example 1.1, 2.4, 3.2 ... ) and we rename the shortcuts (start menu and desktop) to reflect the minor version (for example, app 1.1, app 2.4 )
Question:
Is there a Microsoft UX guideline saying what behavior Windows application should do in that case ?
For example, the Visual Studio shortcut will only display the major version , but not the update number , for example "Visual Studio 2015" and not "Visual Studio 2015 Update 3"
Thanks.
I'd rather be phishing!
|
|
|
|
|
I've never come across a standard convention for this (and I've been around the block a few times  ). Couldn't find one either.
I have seen the convention you have noted "Visual Studio 2015" etc from other major suppliers. By the same token NUnit includes the minor e.g. 2.6.3 as does Windows Phone SDK e.g. 8.1
I'm personally not a fan of changing the shortcut just because there has been an update but I guess you have no choice if you are allowing parallel installs. However that leads me to yet another style (I won't call it a convention any more) that is common and that is to have the Start Menu folder name static with the (major) versions listed below.
Probably not a lot of help, but no-one else responded
|
|
|
|
|
|
We are currently using TFS 2015 for our CI builds. We use the Microsoft unit testing framework that ships with VS 2015 to create our unit tests and we run these as part of our TFS 2015 build process.
We'd like to extend our unit testing to include code coverage. We can't use the VS 2015 / TFS 2015 code coverage tools as these require an enterprise licence and we only have a professional licence (although we would consider upgrading if necessary).
We're looking for a code coverage tool that we can hook into our TFS 2015 build and that produces meaningful output (e.g. coverage reports). If possible it would be good if the same tool integrated into the VS 2015 IDE to give real-time coverage.
All recommendations and suggestions welcome.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
You can use the OpenCover.UI extension for code coverage check inside Visual Studio. https://visualstudiogallery.msdn.microsoft.com/6950a046-8919-4935-8542-c6f37956f688 . It supports MSTest, nUnit and xUnit.
|
|
|
|
|
Since posting my question I've decided to use dotCover from JetBrains as it has a command-line interface that we can use for automating code coverage from within our build process.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Hey this a general question for anyone who is an expert on voip. Want to design a program like viber, but before working with any programmers I wanted to know what initial steps and best languages to use. And if there are any shortcuts to creating it.</
|
|
|
|
|
How to create Custom Control in C#
|
|
|
|
|
|
hellos i want to develop an application that can sell buy advertise farm products online with a registration
|
|
|
|
|
|
|
|
i m working on com port selection part with visual studio windows form. in which i m setting 3 buttons 1. refresh port 2. select port 3. exit. i need these 3 buttons to work in form.....plzzzz help
thank you.
|
|
|
|
|
Member 12472491 wrote: plzzzz help
With what? You have not given us any idea what you have done up to now, or where you are stuck, or indeed, what programming language you are working in. I would suggest you post a properly detailed question in http://www.codeproject.com/Questions/ask.aspx[^] or the appropriate programming forum.
|
|
|
|
|
|
Please elaborate. What do you mean by "dasgvd"?
- Michael Haephrati מיכאל האפרתי
|
|
|
|
|
|
Apart from what Richard said, the question is very much unclear even in Android forums you won't get any help. Why do you want to add an integer value in a array for string, and then what do you want to compare?
Elaborate the question a little more, show a code sample too.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
A vendor has asked me to write a white paper about the barriers that developers encounter in doing code reviews – particularly in regard to getting their managers to care about doing them, or how to sell the boss on adding it to the development process. (Although it’s sponsored, this is written for techies, not a commercial for the vendor… whom I won’t even mention here.)
That is: I plan to write a genuinely-useful document that you want to read all the way through. It might be titled, "7 ways to sell the boss on doing code reviews," or something akin to that.
So here’s my two questions:
• What one thing, ONE THING, do you wish the boss (or powers that be) understood about code review?
• Why did you choose THAT as the one thing to wish for?
Nobody is being quoted here. The closest I might get is to refer to someone indirectly to give the information credibility, something like, “Kim, a programmer at a Midwest insurance company, told me about about the time when….” So you can speak openly (and privately if you’re more comfortable). Though I suspect that this might spark a conversation that’d benefit everybody, so don’t be shy.
It’d help me if you included a LITTLE bit of background for yourself, so I could include that “programmer at an insurance company” attribution, should it back up the text.
Also let me know about your experience with code review. Is it something you use now, but want to improve? Something you’d like to include in your dev process? What difference would it make to get more support from Management for doing code reviews?
Incidentally, if you hate code reviews or just aren’t interested… thanks, but that doesn’t help me write this piece, which does start with the premise that code reviews are valuable. So it’s groovy with me if you don’t find them useful, but I’ll be ignoring that input for the purposes of this white paper.
|
|
|
|
|
I find that code reviews are a vital part of the SDLC. Having another developer review your code is incredibly useful. Developers are human beings, and as such, we can make mistakes or require room for improvement in the work we perform. How many times have you looked at some code and thought "Why did they implement it that way when this way is more more efficient / elegant / conforming to coding stadards" (select as appropriate).
Here's a useful article on what to look for in a code review[^]
If you are introducing code reviews, then you need to ensure that includes everyone - yes even the senior developers who perform code reviews need to have their code reviewed too.
Code reviews increase code quality and ensure coding standards are maintained to name just a few of their benefits.
My biggest question however is why are you having to justify their use in the first place? Anyone who has worked as a software developer in a professional capacity will understand and appreciate their benefits without requiring any persuasion.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I don't need to be sold on the value of code reviews... and I like to think that the developer reading the white paper knows the benefits, too. (Plus, I've written a few articles on the topic, myself.)
My biggest question however is why are you having to justify their use in the first place? Anyone who has worked as a software developer in a professional capacity will understand and appreciate their benefits without requiring any persuasion.
Alas, some people work in environments where the boss had one idea of "the right way to do things" and the developers have a different perception. Sometimes, you need ammunition to change the boss' mind: the benefits as the manager sees them, not the worker-bee. And that's what I aim to write.
|
|
|
|
|
eschindler wrote: I plan to write a genuinely-useful document that you want to read all the way through. It might be titled, "7 ways to sell the boss on doing code reviews," or something akin to that.
So why not just google some studies and argue from the point of cost effectiveness?
Might note as well that code reviews or any process control measures for that matter are not effective unless management actively supports and enforces it.
|
|
|
|
|
Of course I can look at studies. Heck, I've authored a few of those research reports!
But I would far rather hear from individuals who can explain the situations from their own perspective. There's a vast difference in reading, "Twenty percent indicated that they wanted their manager's support," and "I once had a manager whose refusal to listen brought me to tears, when he...."
I can include data from the research reports without asking for assistance. I've been using search engines since Gopher and Archie were newfangled Internet tools.
...But for the human experience? I need people.
|
|
|
|
|
Background - old(ish) grumpy git who worked in UK Financial Services for far too long. Bolshie, argumentative, pretty good at what I did, didn't entirely trust my peer group.
Scenario - "forced" into "SDLC" (yeah, they named their internal process that  )... we all knew what it should be, shame the committee defining the (compulsory) process didn't. It was a disaster waiting to happen, oops, it didn't wait, it happened.
Opportunity - "Volunteers required for training on Peer Review (and how to do it properly)". Me - I'll go for that ... in the back of my mind was sarcasm, mickey-take, etc.
Fact - Training was bl***y good - Takeaway from that = make sure the training is good.
Me - actually this can work, I need to evangelize (exaggerating only a little) ... Takeaway = if the training is good, the grumpy git will get the rest on board
eschindler wrote: What one thing, ONE THING, do you wish the boss (or powers that be) understood about code review?
It's not about blame, putting people down, nit-picking. Ok, not "ONE THING" ... rethink .. Chill60 says: It's not there to find faults, it's there to add QUALITY
eschindler wrote: Why did you choose THAT as the one thing to wish for?
I guess because in my experiences of the "powers that be", it always boils down to someone (else) to blame instead of focussing on making the process better.
The thing I absolutely LOVED about the training process was the insistence that it needed to be completely objective. There were processes put in place to ensure that objectiveness... including timed meetings. All designed to stop anyone being put on the defensive to be honest. I was told at one point to print out the "document" I was reviewing (it's not just about code) and go "find a palm tree". Ok, it was a spindly little tree next to the smoking shelter, but it worked - get away from distractions (Or ... treat the review with respect!)
eschindler wrote: Nobody is being quoted here.
Feel free to include a link to this post (I did say I was a bolshie, grumpy, old git!)
If you need more, just let me know. Can't mention any company names obviously.
Or you could quote me as a "convert to code review"
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
