This question is locked. New answers and comments are not allowed.
Sergej Mertens
Top achievements
Rank 1
Rank 1
Sergej Mertens
asked on 05 Mar 2010, 08:43 AM
Hi,
for all german speaking people interested in JustCode: I wrote a review in my personal Blog at Angetestet: JustCode Beta. Being a ReSharper user since now, I compare JustCode with it. I'm looking forward for comments here or in my Blog.
Greetings,
Daniel
for all german speaking people interested in JustCode: I wrote a review in my personal Blog at Angetestet: JustCode Beta. Being a ReSharper user since now, I compare JustCode with it. I'm looking forward for comments here or in my Blog.
Greetings,
Daniel
3 Answers, 1 is accepted
0
Hello Daniel,
Thanks a lot for taking the time to write this extensive blog post about JustCode. We really appreciate it. Of course such effort should be awarded so we decided to provide you (for free) with a developer license of JustCode with subscription. It will be avaiable in your account next week when we'll release the first official version of JustCode as part of Q1.
I hope you'll continue using JustCode and send us feedback.
I have one comment on the blog post, the color identifiers and the typing assistance features are not disabled by default because they're not fully implemented. We decided to leave them off because many people who are not used to them could find them obtrusive and won't know which exact option to turn off to disable them.
The Typing Assistance has a few flaws that we'll try to fix for the first service pack (beginning of April).
We've already planned a few major features for the Q2 release such as a unit test runner and integration with StyleCop but should you like to give a higher priority to some other feature we'll be glad to hear it,
Once again, thanks for the great feedback.
All the best,
Chris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Thanks a lot for taking the time to write this extensive blog post about JustCode. We really appreciate it. Of course such effort should be awarded so we decided to provide you (for free) with a developer license of JustCode with subscription. It will be avaiable in your account next week when we'll release the first official version of JustCode as part of Q1.
I hope you'll continue using JustCode and send us feedback.
I have one comment on the blog post, the color identifiers and the typing assistance features are not disabled by default because they're not fully implemented. We decided to leave them off because many people who are not used to them could find them obtrusive and won't know which exact option to turn off to disable them.
The Typing Assistance has a few flaws that we'll try to fix for the first service pack (beginning of April).
We've already planned a few major features for the Q2 release such as a unit test runner and integration with StyleCop but should you like to give a higher priority to some other feature we'll be glad to hear it,
Once again, thanks for the great feedback.
All the best,
Chris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
0
Sergej Mertens
Top achievements
Rank 1
Rank 1
answered on 12 Mar 2010, 10:00 AM
Hi Chris,
I'm glad to see development is going on quick. Most important for is the "fix" of typing assistance, that's very annoying atm.
And my feature wishes for the next major release:
1. StyleCop integration: running and auto-fixing messages where possible. Especially adding/replacing file headers and switching a message off in code is very interesting. A tool for assisting the creation of documentation headers would be great (generate headers like GhostDoc but on demand, not auto-fixing).
2. Integration of testing framework: especially MSTest (for me). Testing-Classes should be created on demand and changes to a base class should be reflected to the test classes when possible. Running a special test via context can help getting more productive.
3. I work a lot with LINQ (especially on OpenAccess). I would be happy about seeing a feature like "Transform foreach to LINQ" or something like that - a common task for me in migrated projects. When working with LINQ, Lambdas and/or fluent interfaces, "codelines" could get very long. In that case the on-the-fly error analysis bugs me: it underlines the "line" red and shows the error in tooltip. I can't see the "original" tooltip from IntelliSense anymore.
Thanks,
Daniel
I'm glad to see development is going on quick. Most important for is the "fix" of typing assistance, that's very annoying atm.
And my feature wishes for the next major release:
1. StyleCop integration: running and auto-fixing messages where possible. Especially adding/replacing file headers and switching a message off in code is very interesting. A tool for assisting the creation of documentation headers would be great (generate headers like GhostDoc but on demand, not auto-fixing).
2. Integration of testing framework: especially MSTest (for me). Testing-Classes should be created on demand and changes to a base class should be reflected to the test classes when possible. Running a special test via context can help getting more productive.
3. I work a lot with LINQ (especially on OpenAccess). I would be happy about seeing a feature like "Transform foreach to LINQ" or something like that - a common task for me in migrated projects. When working with LINQ, Lambdas and/or fluent interfaces, "codelines" could get very long. In that case the on-the-fly error analysis bugs me: it underlines the "line" red and shows the error in tooltip. I can't see the "original" tooltip from IntelliSense anymore.
Thanks,
Daniel
0
Hi Daniel,
You nailed it with the first 2 items. They're both with high priority in our product backlog for the Q2 release this year. We're just not sure whether we'll manage to have full StyleCop integration in that timeframe but at least we'll try to cover some of the most used features. We're still hesitating about whether we should give higher priority to the MbUnit or to the xUnit support for the first version. Support for MSTest and NUnit is a must for the first version.
As for the LINQ suggestion - I created a PITS item for this suggestion and you could track its progress here:
http://www.telerik.com/support/pits.aspx#/public/justcode/1340
Most probably we'll be able to include it in our plans after the Q2 release.
Best wishes,
Chris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
You nailed it with the first 2 items. They're both with high priority in our product backlog for the Q2 release this year. We're just not sure whether we'll manage to have full StyleCop integration in that timeframe but at least we'll try to cover some of the most used features. We're still hesitating about whether we should give higher priority to the MbUnit or to the xUnit support for the first version. Support for MSTest and NUnit is a must for the first version.
As for the LINQ suggestion - I created a PITS item for this suggestion and you could track its progress here:
http://www.telerik.com/support/pits.aspx#/public/justcode/1340
Most probably we'll be able to include it in our plans after the Q2 release.
Best wishes,
Chris
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.