|
You can change any TFS query using the Query Editor, and add further details like the parent PBI, which should give more information, or assigned to etc.
When you click on MyTasks query, Default is "Results", which the result of your query, and the below window shows details of the work items. To edit the query, navigate to the "Editor" link. Here, you can change the Type of Query to use Tree of work items, which gives you nested results. OR work items & direct links, which helps you present all the links to your work item.
Thanks,
Ajay Bhosle
http://dralm.blogspot.in
|
|
|
|
|
It should not take longer than 5 minutes and does not require from you any demographic data other than stating whether youre developer or agile coach.
The link to survey is: http://educ.sphinxonline.net/v4/s/cribkm[^]
Thank you for your help!!!
|
|
|
|
|
Your link does not work.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I'm wondering how other people manage common, utility or shared code?
Say some extension method's etc.
Do you just add a file with this code and share it amongst your projects?
Do you have a snippet type program and just copy/paste into/out of that?
Or do you build up a separate library and reference that?
If you do the latter how much do you put in, i.e. do you think there's an issue with that library containing much more code than you need?
|
|
|
|
|
By definition common code can not be snippet - snippet is for repeated code structures not for repeated code!
IMHO the best way is a separate library. I'm also do such utility methods stateless an static.
I'm also think that there is no such a thing too large library - it only a matter of code organization. There is nothing wrong with a single library with thousands of methods (if the project requests it) as long as the methods are organized...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Thanks for that, I went down that route, and created a set of libraries by function (IO/data/etc) rather than one large single library.
|
|
|
|
|
You may consider an other addition to that...
I'm creating my libraries in a totally different solution (no as part of my main development solution) than create a local nuget package from the outcome and add it as reference - that handles me all the necessary dependencies an updates every time I update the util libraries...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
|
|
|
|
|
Similar to Eliyahu, I prefer a Utility library for such code. I'd write one file for each type which gets extended by an extension method (my way of code organisation). Similarly, other utility methods get grouped into files by their underlying business object.
|
|
|
|
|
Depends.
First, one be sure that the shared code really should be shared. The fact that it seems like it is common functionality doesn't necessarily mean that it will remain that way. (Really a bad idea to start adding conditional logic to control different logic flows due to different applications.)
Second, how is the rest of the business applications structured. Primary if you have two applications X and Y that you want to use your common code M, do X and Y have their own delivery schedules or are they always delivered together. If they have their own deliver schedules then a common library MUST have its own delivery schedule as well. That is the only way to insure that X is using the version of M that it was developed with and Y is doing the same.
Third if different deliver schedules are needed then one must deal with different versioned apps, and if one must deal with git as the source control system then one has a problem since git only deals with that via different repositories.
There are additional issues depending on what language is being used and how applications are delivered.
|
|
|
|
|
I have a separate project in my solution that contains such code i.e. code that is shared across other parts of the application. This can then be distributed as a self contained assembly. If using .NET then you have the option of placing this assembly in the GAC where other applications can also use the same functionality.
|
|
|
|
|
We have probably all developed those Visual Studio applications which rely on additional DLLs and static libraries containing our favorite snippets of code. My question is how best to manage this kind of project which is not all neatly contained in the project folder. If we add our library paths (elsewhere on the disk) to the project then we can be sure that we are linking with the latest versions of the libraries but archiving this arrangement is a nightmare. Another alternative might be to copy all the libs to a 'lib' folder within the application that we are developing. This would provide a self-contained project which could easily be archived but we may not be using the latest version of our libs.
I would be very interested to hear what other developers do. Is there a better way! 
Thanks
Tony
|
|
|
|
|
|
softwaremonkey wrote: but we may not be using the latest version of our libs.
However you will in fact be using the same one in development, QA and production. And be more likely to label it in source control so you can keep track of it.
Thus if a problem occurs in QA or production then you are more likely to be able to reproduce it. And when you do update to new versions as part of a development and business decision then development and QA can more fully verity that it continues to work as expected.
|
|
|
|
|
Thanks, that is a very good point and a compelling reason to 'ring fence' every file needed to build a particular version of an application including the libraries.
|
|
|
|
|
Try setting up your own nuget repository, especially if you share components across projects
|
|
|
|
|
Can anyone share me information about ALM tool users and their usage level ?
Its urgent   i tried my best in researching it....looking up for someone to help me with this
|
|
|
|
|
oberon29 wrote: Its urgent
We're volunteers. You can't hurry volunteers, it's not urgent here.
I don't think anyone measured the usage-level of various application lifecycle management tools. You could consult Google to find out what's most used.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Quote:
Source Error:
Line 948: <panelcollection>
Line 949:<dx:panelcontent id="PanelContent1" runat="server" supportsdisabledattribute="True">
Line 950: <dx:aspxpagecontrol id="ASPxPageControl3" runat="server" activetabindex="1"
line="" 951:="" width="100%" cssfilepath="~/App_Themes/Glass/{0}/styles.css" 952:="" csspostfix="Glass" spritecssfilepath="~/App_Themes/Glass/{0}/sprite.css" <="" blockquote="">
|
|
|
|
|
What is this supposed to mean?
Veni, vidi, abiit domum
|
|
|
|
|
what's that namespace "dx" ? are you using some third party control like "devx" ?
Nikhil Singh
|
|
|
|
|
This may be a dev express error
Sankarsan Parida
|
|
|
|
|
Hi...I want to know what exactly is the application life cycle and what are its steps.thanks.
|
|
|
|
|
Have you used google before?
|
|
|
|
|
No it is a beta product.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
An Application lifecycle is, well... The Lifecycle of an application.
It typically starts with governance, then follows the development and afterwards the application goes into maintenance, where only support, bugfixes and maybe updates are delivered.
See Wikipedia for more details[^]
Veni, vidi, caecus | Everything summarizes to Assembly code
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
