My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Yesterday

  • 34 hours ago
    issue 152 (Provide spell checking in ASPX , XAML files.) reported by Roland.Baranowski   -   It would be nice if the spell check in ASPX, XAML files was available.
    It would be nice if the spell check in ASPX, XAML files was available.

Last 30 days

  • Dec 09, 2009
    issue 151 (Agent Smith wants to rename standard ASP.Net functions) reported by kris.hargrave   -   What steps will reproduce the problem? 1. Having the following line in your ASP.Net code 2. protected void Page_Load(object sender, EventArgs e) What is the expected behavior? What do you see instead? Ignore standard ASP.Net methods like Page_Load, Render, etc What version of ReSharper, Visual Studio and Windows do you use? ReSharper 4.5, Agent Smith 1.4.031669, Visual studio 2008 Please provide any additional information below. Maybe an easy way to add functions names that can be ignored, I understand that names shouldn't have an _ but... I don't see how to avoid it with the ASP.Net framework. I'm still pretty new to this program, so maybe I did miss something
    What steps will reproduce the problem? 1. Having the following line in your ASP.Net code 2. protected void Page_Load(object sender, EventArgs e) What is the expected behavior? What do you see instead? Ignore standard ASP.Net methods like Page_Load, Render, etc What version of ReSharper, Visual Studio and Windows do you use? ReSharper 4.5, Agent Smith 1.4.031669, Visual studio 2008 Please provide any additional information below. Maybe an easy way to add functions names that can be ignored, I understand that names shouldn't have an _ but... I don't see how to avoid it with the ASP.Net framework. I'm still pretty new to this program, so maybe I did miss something

Earlier this year

  • Nov 04, 2009
    issue 47 (VB version?) commented on by forever.zet   -   R# calls DaemonProcess class, which calls CommentsAnalizer, which performs spell checking
    R# calls DaemonProcess class, which calls CommentsAnalizer, which performs spell checking
  • Nov 04, 2009
    issue 47 (VB version?) commented on by petr.kuzel   -   I wanted to dig out a subset of functionality XML comments spell checker. I checked out AgentSmith and looked over code. I discovered attributes at assembly level and few [QuickFix] on other classes and Actions.Xml. Still I have not identified where are respective R# entry points, how to build and deploy.
    I wanted to dig out a subset of functionality XML comments spell checker. I checked out AgentSmith and looked over code. I discovered attributes at assembly level and few [QuickFix] on other classes and Actions.Xml. Still I have not identified where are respective R# entry points, how to build and deploy.
  • Nov 03, 2009
    issue 150 (Don't check spelling in string literals used as arguments fo...) reported by drewnoakes   -   This code raises a spell check error because 'adca' is not a known word. new Guid("012454a3-6014-4339-adca-b5026ad6c937") I'd like to have a list of known parameters for which string literal arguments are ignored. The Guid example is the one I come upon most often. Note that I wouldn't expect this to be too clever -- the following would still warn: var s = "012454a3-6014-4339-adca-b5026ad6c937"; new Guid(s); Is it possible to extend the ReSharper value analysis attribute set such that I can add this attribute in both internal and external annotations, just like I can with [NotNull] and [CanBeNull]?
    This code raises a spell check error because 'adca' is not a known word. new Guid("012454a3-6014-4339-adca-b5026ad6c937") I'd like to have a list of known parameters for which string literal arguments are ignored. The Guid example is the one I come upon most often. Note that I wouldn't expect this to be too clever -- the following would still warn: var s = "012454a3-6014-4339-adca-b5026ad6c937"; new Guid(s); Is it possible to extend the ReSharper value analysis attribute set such that I can add this attribute in both internal and external annotations, just like I can with [NotNull] and [CanBeNull]?
  • Nov 03, 2009
    issue 149 (Request: Pattern for Comment-Stubs) reported by nebria80   -   Hi, I would like to enter a template for the comment stubs e.g. a todo marker and the macro for the current username. Regards, Nebria
    Hi, I would like to enter a template for the comment stubs e.g. a todo marker and the macro for the current username. Regards, Nebria
  • Oct 26, 2009
    issue 138 (Add formatting rules for xml elements) commented on by drewnoakes   -   I seem to recall reading that ReSharper 5 will have some support for formatting of XML. I agree though that this is sorely needed, especially since doing more WPF work in the last 6 months.
    I seem to recall reading that ReSharper 5 will have some support for formatting of XML. I agree though that this is sorely needed, especially since doing more WPF work in the last 6 months.
  • Oct 26, 2009
    issue 148 (Spelling search and corrections should behave differently fo...) reported by drewnoakes   -   For example, I have a method "GetTodaysIoiData". Agent Smith points out that "Todays" is not a word, yet "Today's" is. So it suggests renaming the method as "GetToday'sIoiData" which is valid in string literals/documentation, but invalid in identifiers. In fact, when matching identifiers, Agent Smith should exclude hyphens and apostrophes from matching. If this occurred, then this particular error would only occur in string literals/documentation. I've also seen cases where R# suggests replacing an unknown substring with something that contains whitespace or hyphens. An example of this is "Parsable" (able to be parsed). This, and many other similar words, are commonplace to programmers. Agent Smith suggests "Pars able" which again is reasonable in a literal/documentation, but not an identifier. - R# 4.5 - Windows XP - VS 2008 (9.0.21022.8 RTM)
    For example, I have a method "GetTodaysIoiData". Agent Smith points out that "Todays" is not a word, yet "Today's" is. So it suggests renaming the method as "GetToday'sIoiData" which is valid in string literals/documentation, but invalid in identifiers. In fact, when matching identifiers, Agent Smith should exclude hyphens and apostrophes from matching. If this occurred, then this particular error would only occur in string literals/documentation. I've also seen cases where R# suggests replacing an unknown substring with something that contains whitespace or hyphens. An example of this is "Parsable" (able to be parsed). This, and many other similar words, are commonplace to programmers. Agent Smith suggests "Pars able" which again is reasonable in a literal/documentation, but not an identifier. - R# 4.5 - Windows XP - VS 2008 (9.0.21022.8 RTM)
  • Oct 19, 2009
    ChangeLog Wiki page edited by forever.zet   -   Revision r293 Edited wiki page through web user interface.
    Revision r293 Edited wiki page through web user interface.
  • Oct 19, 2009
    ChangeLog Wiki page edited by forever.zet   -   Revision r292 Edited wiki page through web user interface.
    Revision r292 Edited wiki page through web user interface.
  • Oct 19, 2009
    ChangeLog Wiki page edited by forever.zet   -   Revision r291 Edited wiki page through web user interface.
    Revision r291 Edited wiki page through web user interface.
  • Oct 19, 2009
    Agent Smith 1.4.0 Setup (R# 5.0).msi (Agent Smith 1.4.0 Setup (R# 5.0).msi) file uploaded by forever.zet   -  
    Labels: Featured
    Labels: Featured
  • Oct 19, 2009
    Agent Smith 1.4.0 Setup (R# 4.5).msi (Agent Smith 1.4.0 Setup (R# 4.5).msi) file uploaded by forever.zet   -  
    Labels: Featured
    Labels: Featured
  • Oct 19, 2009
    r290 ([No log message]) committed by forever.zet   -   [No log message]
    [No log message]
  • Oct 19, 2009
    r289 ([No log message]) committed by forever.zet   -   [No log message]
    [No log message]
  • Oct 19, 2009
    r288 ([No log message]) committed by forever.zet   -   [No log message]
    [No log message]
  • Oct 19, 2009
    r287 ([No log message]) committed by forever.zet   -   [No log message]
    [No log message]
  • Oct 06, 2009
    r286 (Fixed SmartPaste Added surround with <see langref) committed by forever.zet   -   Fixed SmartPaste Added surround with <see langref
    Fixed SmartPaste Added surround with <see langref
  • Sep 28, 2009
    issue 147 (Needs a way to separate between implicit and explicit interf...) reported by sideritezaqwedcxs   -   An interface can be explicitly specified and, in that case, the implementation can be private like: void MyInterface.MyMember In that case the Agent Smith code naming conventions would warn that the private properties and methods should start with a lowercase letter (these are my settings). I could find no way of differentiating between normal private methods and the explicit interface implementation.
    An interface can be explicitly specified and, in that case, the implementation can be private like: void MyInterface.MyMember In that case the Agent Smith code naming conventions would warn that the private properties and methods should start with a lowercase letter (these are my settings). I could find no way of differentiating between normal private methods and the explicit interface implementation.
  • Sep 23, 2009
    issue 146 (XML comment not recognized if there is a precompiler directi...) reported by gael.fraiteur   -   What steps will reproduce the problem? /// <summary> /// Base class for all aspects that are declared using custom attributes /// (<see cref="MulticastAttribute"/>). /// </summary> /// <remarks> /// <para>All classes derived from <see cref="Aspect"/> should be serializable /// (using the <see cref="SerializableAttribute"/> custom attribute). Fields that /// are only used at runtime (and unknown at compile-time) should be carefully /// marked with the <see cref="NonSerializedAttribute"/> custom attribute.</para> /// </remarks> #if !SMALL [Serializable] #endif [SuppressMessage("Microsoft.Naming", "CA1710" /* IdentifiersShouldHaveCorrectSuffix */)] [RequirePostSharp(null, "AspectWeaver")] [XmlType(Namespace = XmlNamespace)] public abstract class Aspect : MulticastAttribute, IAspect What is the expected behavior? What do you see instead? Expected: word 'Aspect' should NOT be underlined in green. It is. What version of ReSharper, Visual Studio and Windows do you use? Resharper 4.5.1274.1, Visual Studio 2008 SP1, Windows 7 Please provide any additional information below. It behaves correctly when the precompiler directive is commented out.
    What steps will reproduce the problem? /// <summary> /// Base class for all aspects that are declared using custom attributes /// (<see cref="MulticastAttribute"/>). /// </summary> /// <remarks> /// <para>All classes derived from <see cref="Aspect"/> should be serializable /// (using the <see cref="SerializableAttribute"/> custom attribute). Fields that /// are only used at runtime (and unknown at compile-time) should be carefully /// marked with the <see cref="NonSerializedAttribute"/> custom attribute.</para> /// </remarks> #if !SMALL [Serializable] #endif [SuppressMessage("Microsoft.Naming", "CA1710" /* IdentifiersShouldHaveCorrectSuffix */)] [RequirePostSharp(null, "AspectWeaver")] [XmlType(Namespace = XmlNamespace)] public abstract class Aspect : MulticastAttribute, IAspect What is the expected behavior? What do you see instead? Expected: word 'Aspect' should NOT be underlined in green. It is. What version of ReSharper, Visual Studio and Windows do you use? Resharper 4.5.1274.1, Visual Studio 2008 SP1, Windows 7 Please provide any additional information below. It behaves correctly when the precompiler directive is commented out.
  • Sep 21, 2009
    issue 145 (Out of Memory Exception) reported by hype8912   -   Pressed semi-colon and it threw error. ReSharper 4.5 Version=4.5.1274.1, Edition=, Built=2009-07-21T19:01:06, Configuration=ReSharper_AddIn, VsVersion=9.0 Current file extension: cs Previous exception:OutOfMemoryException : Exception of type 'System.OutOfMemoryException' was thrown. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Collections.Generic.Dictionary`2.Resize() at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.NodeTypeCounter.GetIndex (NodeType nodeType) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\NodeTypeCounter.cs:line 20 at JetBrains.ReSharper.Psi.Parsing.TokenNodeType..ctor(String s) in c:\Agent\work\6f6005be76df46e2\src\Psi\src\parsing\TokenNodeType.cs:line 8 at AgentSmith.SpellCheck.TokenNodeTypeBase..ctor(String name) in d:\Projects\as\src\AgentSmith\SpellCheck\TokenNodeTypeBase.cs:line 11 at AgentSmith.SpellCheck.WordLexer.WordTokenType..ctor() in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 108 at AgentSmith.SpellCheck.WordLexer..ctor(String data) in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 14 at AgentSmith.Comments.CommentAnalyzer.<getWordsFromXmlComment>d__0.MoveNext () in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 174 at AgentSmith.Comments.CommentAnalyzer.checkCommentSpelling (IClassMemberDeclaration decl, ICollection`1 highlightings, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 80 at AgentSmith.Comments.CommentAnalyzer.Analyze(IDeclaration declaration, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 51 at AgentSmith.DaemonProcess.ProcessBeforeInterior(IElement element) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 100 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 72 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at AgentSmith.DaemonProcess.ProcessFile(ICSharpFile file) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 174 at AgentSmith.DaemonProcess.Execute(Action`1 action) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 67 at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 176 — End of inner exception stack trace — LoggerException: Exception of type 'System.OutOfMemoryException' was thrown. -> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Collections.Generic.Dictionary`2.Resize() at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.NodeTypeCounter.GetIndex (NodeType nodeType) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\NodeTypeCounter.cs:line 20 at JetBrains.ReSharper.Psi.Parsing.TokenNodeType..ctor(String s) in c:\Agent\work\6f6005be76df46e2\src\Psi\src\parsing\TokenNodeType.cs:line 8 at AgentSmith.SpellCheck.TokenNodeTypeBase..ctor(String name) in d:\Projects\as\src\AgentSmith\SpellCheck\TokenNodeTypeBase.cs:line 11 at AgentSmith.SpellCheck.WordLexer.WordTokenType..ctor() in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 108 at AgentSmith.SpellCheck.WordLexer..ctor(String data) in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 14 at AgentSmith.Comments.CommentAnalyzer.<getWordsFromXmlComment>d__0.MoveNext () in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 174 at AgentSmith.Comments.CommentAnalyzer.checkCommentSpelling (IClassMemberDeclaration decl, ICollection`1 highlightings, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 80 at AgentSmith.Comments.CommentAnalyzer.Analyze(IDeclaration declaration, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 51 at AgentSmith.DaemonProcess.ProcessBeforeInterior(IElement element) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 100 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 72 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at AgentSmith.DaemonProcess.ProcessFile(ICSharpFile file) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 174 at AgentSmith.DaemonProcess.Execute(Action`1 action) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 67 at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 176 — End of Inner Exception Stack Trace — at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 196 at JetBrains.ReSharper.Daemon.Impl.VisibleDocumentDaemonProcess.DoHighlighting (Boolean globalAnalysisStages) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 238 at JetBrains.ReSharper.Daemon.Impl.VisibleDocumentDaemonProcess.<>c_DisplayCla ss3.<EnqueueHighlightingJob>b_1() in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 209 at JetBrains.ReSharper.Daemon.Impl.DaemonThreadImpl.DaemonThreadProc() in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonThreadImpl.cs:line 119 at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() Getting an out of exception error randomly. Usually after it's been open for 4 or 5 hours. VS 2008 SP1 Resharper 4.5 -Agent Smith -Agent Johnson Ants Profiler 5 http://www.jetbrains.net/jira/browse/RSRP-122181 http://www.jetbrains.net/jira/browse/RSRP-122182
    Pressed semi-colon and it threw error. ReSharper 4.5 Version=4.5.1274.1, Edition=, Built=2009-07-21T19:01:06, Configuration=ReSharper_AddIn, VsVersion=9.0 Current file extension: cs Previous exception:OutOfMemoryException : Exception of type 'System.OutOfMemoryException' was thrown. System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Collections.Generic.Dictionary`2.Resize() at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.NodeTypeCounter.GetIndex (NodeType nodeType) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\NodeTypeCounter.cs:line 20 at JetBrains.ReSharper.Psi.Parsing.TokenNodeType..ctor(String s) in c:\Agent\work\6f6005be76df46e2\src\Psi\src\parsing\TokenNodeType.cs:line 8 at AgentSmith.SpellCheck.TokenNodeTypeBase..ctor(String name) in d:\Projects\as\src\AgentSmith\SpellCheck\TokenNodeTypeBase.cs:line 11 at AgentSmith.SpellCheck.WordLexer.WordTokenType..ctor() in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 108 at AgentSmith.SpellCheck.WordLexer..ctor(String data) in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 14 at AgentSmith.Comments.CommentAnalyzer.<getWordsFromXmlComment>d__0.MoveNext () in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 174 at AgentSmith.Comments.CommentAnalyzer.checkCommentSpelling (IClassMemberDeclaration decl, ICollection`1 highlightings, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 80 at AgentSmith.Comments.CommentAnalyzer.Analyze(IDeclaration declaration, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 51 at AgentSmith.DaemonProcess.ProcessBeforeInterior(IElement element) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 100 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 72 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at AgentSmith.DaemonProcess.ProcessFile(ICSharpFile file) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 174 at AgentSmith.DaemonProcess.Execute(Action`1 action) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 67 at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 176 — End of inner exception stack trace — LoggerException: Exception of type 'System.OutOfMemoryException' was thrown. -> System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown. at System.Collections.Generic.Dictionary`2.Resize() at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.NodeTypeCounter.GetIndex (NodeType nodeType) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\NodeTypeCounter.cs:line 20 at JetBrains.ReSharper.Psi.Parsing.TokenNodeType..ctor(String s) in c:\Agent\work\6f6005be76df46e2\src\Psi\src\parsing\TokenNodeType.cs:line 8 at AgentSmith.SpellCheck.TokenNodeTypeBase..ctor(String name) in d:\Projects\as\src\AgentSmith\SpellCheck\TokenNodeTypeBase.cs:line 11 at AgentSmith.SpellCheck.WordLexer.WordTokenType..ctor() in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 108 at AgentSmith.SpellCheck.WordLexer..ctor(String data) in d:\Projects\as\src\AgentSmith\SpellCheck\WordLexer.cs:line 14 at AgentSmith.Comments.CommentAnalyzer.<getWordsFromXmlComment>d__0.MoveNext () in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 174 at AgentSmith.Comments.CommentAnalyzer.checkCommentSpelling (IClassMemberDeclaration decl, ICollection`1 highlightings, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 80 at AgentSmith.Comments.CommentAnalyzer.Analyze(IDeclaration declaration, Boolean spellCheck) in d:\Projects\as\src\AgentSmith\Comments\CommentAnalyzer.cs:line 51 at AgentSmith.DaemonProcess.ProcessBeforeInterior(IElement element) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 100 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 72 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at JetBrains.ReSharper.Psi.ExtensionsAPI.Tree.TreeElement.ProcessDescendants (IRecursiveElementProcessor processor) in c:\Agent\work\6f6005be76df46e2 \src\Psi\src\ExtensionsAPI\Tree\TreeElement.cs:line 74 at AgentSmith.DaemonProcess.ProcessFile(ICSharpFile file) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 174 at AgentSmith.DaemonProcess.Execute(Action`1 action) in d:\Projects\as\src\AgentSmith\DaemonProcess.cs:line 67 at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 176 — End of Inner Exception Stack Trace — at JetBrains.ReSharper.Daemon.Impl.DaemonProcessBase.DoHighlighting (DaemonProcessKind kind, Action`1 commiter) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonProcessBase.cs:line 196 at JetBrains.ReSharper.Daemon.Impl.VisibleDocumentDaemonProcess.DoHighlighting (Boolean globalAnalysisStages) in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 238 at JetBrains.ReSharper.Daemon.Impl.VisibleDocumentDaemonProcess.<>c_DisplayCla ss3.<EnqueueHighlightingJob>b_1() in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\VisibleDocumentDaemonProcess.cs:line 209 at JetBrains.ReSharper.Daemon.Impl.DaemonThreadImpl.DaemonThreadProc() in c:\Agent\work\6f6005be76df46e2 \src\Daemon\src\Impl\DaemonThreadImpl.cs:line 119 at System.Threading.ThreadHelper.ThreadStart_Context(Object state) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() Getting an out of exception error randomly. Usually after it's been open for 4 or 5 hours. VS 2008 SP1 Resharper 4.5 -Agent Smith -Agent Johnson Ants Profiler 5 http://www.jetbrains.net/jira/browse/RSRP-122181 http://www.jetbrains.net/jira/browse/RSRP-122182
  • Sep 10, 2009
    issue 144 (<see langword="..."/> instead of <c>...</c>) reported by nebria80   -   Hi, I don't know if its really an issue or if I justed missed something. Is there some way to configure what metatag AgentSmith shall use for identifiers oder keywords? Currently its using <c></c> I wonder if there is some "official" guide what to use when. I've seen some sourcecomments by Microsoft using <see langword="..."/>. Best regards
    Hi, I don't know if its really an issue or if I justed missed something. Is there some way to configure what metatag AgentSmith shall use for identifiers oder keywords? Currently its using <c></c> I wonder if there is some "official" guide what to use when. I've seen some sourcecomments by Microsoft using <see langword="..."/>. Best regards
  • Sep 09, 2009
    issue 143 (VB.NET Support for naming conventions) commented on by forever.zet   -   I have no plans currently to implement VB.Net support, but if somebody whants to do it - I would encourage that :)
    I have no plans currently to implement VB.Net support, but if somebody whants to do it - I would encourage that :)
  • Sep 08, 2009
    issue 143 (VB.NET Support for naming conventions) reported by marouanebouzoubaa   -   What steps will reproduce the problem? 1. Create VB.NET Project 2. Create private field: Dim EntityBL As String 3. Create Method:Function toto(ByVal MP As String, ByVal po As String, ByVal _ti As Integer) As String What is the expected behavior? What do you see instead? What version of ReSharper, Visual Studio and Windows do you use? 1274.1 Please provide any additional information below.
    What steps will reproduce the problem? 1. Create VB.NET Project 2. Create private field: Dim EntityBL As String 3. Create Method:Function toto(ByVal MP As String, ByVal po As String, ByVal _ti As Integer) As String What is the expected behavior? What do you see instead? What version of ReSharper, Visual Studio and Windows do you use? 1274.1 Please provide any additional information below.
  • Aug 28, 2009
    issue 142 (Add enqueuing to us dictionary) reported by zippy1981   -   Equeuing is not in the dictionary. Its a valid word.
    Equeuing is not in the dictionary. Its a valid word.
  • Aug 18, 2009
    issue 111 (Spell checker doesn’t save new words to the dictionary) commented on by dukes.brian   -   Same issue here Agent Smith 1.3.8.39068 ReSharper 4.5.1274.1 VS 2008 SP1 9.0.30729.1 SP Windows Vista SP2
    Same issue here Agent Smith 1.3.8.39068 ReSharper 4.5.1274.1 VS 2008 SP1 9.0.30729.1 SP Windows Vista SP2
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r285 Edited wiki page through web user interface.
    Revision r285 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r284 Edited wiki page through web user interface.
    Revision r284 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r283 Edited wiki page through web user interface.
    Revision r283 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r282 Edited wiki page through web user interface.
    Revision r282 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r281 Edited wiki page through web user interface.
    Revision r281 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r280 Edited wiki page through web user interface.
    Revision r280 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r279 Edited wiki page through web user interface.
    Revision r279 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page edited by forever.zet   -   Revision r278 Edited wiki page through web user interface.
    Revision r278 Edited wiki page through web user interface.
  • Aug 02, 2009
    Reflow Wiki page added by forever.zet   -   Revision r277 Created wiki page through web user interface.
    Revision r277 Created wiki page through web user interface.
  • Jul 24, 2009
    issue 141 (Smart paste not functioning) reported by karlmayer   -   What steps will reproduce the problem? 1. Paste text with new lines into XML comment What is the expected behavior? What do you see instead? I expect each new line to be prefixed with ///, but it pasted as normal. What version of ReSharper, Visual Studio and Windows do you use? Visual Studio 2008 SP1, ReSharper 4.5, Windows XP Please provide any additional information below.
    What steps will reproduce the problem? 1. Paste text with new lines into XML comment What is the expected behavior? What do you see instead? I expect each new line to be prefixed with ///, but it pasted as normal. What version of ReSharper, Visual Studio and Windows do you use? Visual Studio 2008 SP1, ReSharper 4.5, Windows XP Please provide any additional information below.
  • Jul 22, 2009
    issue 138 (Add formatting rules for xml elements) commented on by dfayerma   -   1. line break before/after, remove break before/after: >Will these options affect root elements only, all elements or configurable elements? I think these options would affect configurable elements. Allow to configure separate sets of options for each element. 2. indent content >Will this work this way? <summary> Paragraph One. Paragraph Two. </summary> -> <summary> Paragraph One. Paragraph Two. </summary> >So bacically will it just shift entire contents of root elements only? Yes. >Shall we allow specifying number of tabs/spaces to indent? Good point. This shoudl be configurable. 3. Align tags How will be this case handled? <a>asdfsdf</a> >I think this shall relate only to tags found in the beginning of a line. I Agree, maybe this option should only be enabled if line break before and after the element is selected.
    1. line break before/after, remove break before/after: >Will these options affect root elements only, all elements or configurable elements? I think these options would affect configurable elements. Allow to configure separate sets of options for each element. 2. indent content >Will this work this way? <summary> Paragraph One. Paragraph Two. </summary> -> <summary> Paragraph One. Paragraph Two. </summary> >So bacically will it just shift entire contents of root elements only? Yes. >Shall we allow specifying number of tabs/spaces to indent? Good point. This shoudl be configurable. 3. Align tags How will be this case handled? <a>asdfsdf</a> >I think this shall relate only to tags found in the beginning of a line. I Agree, maybe this option should only be enabled if line break before and after the element is selected.
  • Jul 22, 2009
    issue 140 (Outlining: Expand all comments) Status changed by forever.zet   -  
    Status: Accepted
    Status: Accepted
  • Jul 22, 2009
    issue 139 (Add an action to format all comments in a current file) Status changed by forever.zet   -  
    Status: Accepted
    Status: Accepted
  • Jul 22, 2009
    issue 138 (Add formatting rules for xml elements) Status changed by forever.zet   -   1. line break before/after, remove break before/after: Will these options affect root elements only, all elements or configurable elements? So in your example, I'd want to insert breaks after/before <summary> and <para>, after <br/> but I'd like to remove break after and before <c> 2. indent content Will this work this way? <summary> Paragraph One. Paragraph Two. </summary> -> <summary> Paragraph One. Paragraph Two. </summary> So bacically will it just shift entire contents of root elements only? Shall we allow specifying number of tabs/spaces to indent? 3. Align tags How will be this case handled? <a>asdfsdf</a> I think this shall relate only to tags found in the beginning of a line.
    Status: Accepted
    1. line break before/after, remove break before/after: Will these options affect root elements only, all elements or configurable elements? So in your example, I'd want to insert breaks after/before <summary> and <para>, after <br/> but I'd like to remove break after and before <c> 2. indent content Will this work this way? <summary> Paragraph One. Paragraph Two. </summary> -> <summary> Paragraph One. Paragraph Two. </summary> So bacically will it just shift entire contents of root elements only? Shall we allow specifying number of tabs/spaces to indent? 3. Align tags How will be this case handled? <a>asdfsdf</a> I think this shall relate only to tags found in the beginning of a line.
    Status: Accepted
  • Jul 22, 2009
    issue 139 (Add an action to format all comments in a current file) commented on by forever.zet   -   I think it would be also nice to try to include it into ReSharper's list of code cleanup tasks so it could be done along with file reformatting.
    I think it would be also nice to try to include it into ReSharper's list of code cleanup tasks so it could be done along with file reformatting.
  • Jul 21, 2009
    issue 140 (Outlining: Expand all comments) reported by dfayerma   -   Add a menu item and keyboard shortcut to "Expand all Comments". This would allow to review design of a class with all implementations collapsed but comments expanded. This is also very useful when reviewing comments.
    Add a menu item and keyboard shortcut to "Expand all Comments". This would allow to review design of a class with all implementations collapsed but comments expanded. This is also very useful when reviewing comments.
  • Jul 21, 2009
    issue 139 (Add an action to format all comments in a current file) reported by dfayerma   -   Add a menu item and/or keyboard shortcut to format all comments in current document.
    Add a menu item and/or keyboard shortcut to format all comments in current document.
  • Jul 21, 2009
    issue 138 (Add formatting rules for xml elements) changed by dfayerma   -   Changed status to New pending approval from forever.zet
    Summary: Add formatting rules for xml elements
    Status: New
    Labels: Type-Enhancement
    Changed status to New pending approval from forever.zet
    Summary: Add formatting rules for xml elements
    Status: New
    Labels: Type-Enhancement
  • Jul 21, 2009
    issue 138 (Enhancement: Add formatting rules for xml elements) reported by dfayerma   -   Allow to specify formatting rules for xml elements. Similar to Resharper formatting rules user would be able to add new elements to the list on the AgentSmith configuration page. Options for each element would include the following check boxes: - line break before - line break after - indent content - align begin and end tags - remove line break before - remove line break after This would allow to format comments as: /// <summary> /// Some summary for the method that may be /// multi-line with <br/> /// line break. /// <para> /// And paragraph that may not be indented. /// </para> /// </summary> /// <param name="parent"> /// The parameter description /// </param> /// <exception cref="ArgumentNullException"> /// If the required <c>parent</c> argument is <c>null</c>. /// </exception> Or compressed style as described in issue 86 http://code.google.com/p/agentsmithplugin/issues/detail?id=86 Current AgentSmith functionality does preserve formatting entered in the example above but I think it would be very useful if it formatted the comments if configured that way by the user.
    Allow to specify formatting rules for xml elements. Similar to Resharper formatting rules user would be able to add new elements to the list on the AgentSmith configuration page. Options for each element would include the following check boxes: - line break before - line break after - indent content - align begin and end tags - remove line break before - remove line break after This would allow to format comments as: /// <summary> /// Some summary for the method that may be /// multi-line with <br/> /// line break. /// <para> /// And paragraph that may not be indented. /// </para> /// </summary> /// <param name="parent"> /// The parameter description /// </param> /// <exception cref="ArgumentNullException"> /// If the required <c>parent</c> argument is <c>null</c>. /// </exception> Or compressed style as described in issue 86 http://code.google.com/p/agentsmithplugin/issues/detail?id=86 Current AgentSmith functionality does preserve formatting entered in the example above but I think it would be very useful if it formatted the comments if configured that way by the user.
  • Jul 18, 2009
    Contributors Wiki page edited by forever.zet
  • Jul 18, 2009
    issue 135 (Reflow logic does not calculate max length correctly ) commented on by forever.zet   -   There is almost no process. New features must relate to what Agent Smith does - Coding Standards, Naming Conventions, Error Checking, Documentation ... The feature shall be useful to more or less large audience. And I would also like to review it :) Usually I checkin into 4.5 branch and when I'm ready to release I tag it. I think that's it.
    There is almost no process. New features must relate to what Agent Smith does - Coding Standards, Naming Conventions, Error Checking, Documentation ... The feature shall be useful to more or less large audience. And I would also like to review it :) Usually I checkin into 4.5 branch and when I'm ready to release I tag it. I think that's it.
  • Jul 16, 2009
    issue 135 (Reflow logic does not calculate max length correctly ) commented on by dfayerma   -   Thanks. That would be great! What is your process for contributing new features? Dimitry
    Thanks. That would be great! What is your process for contributing new features? Dimitry
  • Jul 16, 2009
    issue 127 (Provide surrounding with <c></c> for null keyword.) Status changed by forever.zet   -   Fixed in 1.3.8 I've added suggestion only for the mentioned words because other keywords appear often as regular words and highlighting for them would be annoying.
    Status: Fixed
    Fixed in 1.3.8 I've added suggestion only for the mentioned words because other keywords appear often as regular words and highlighting for them would be annoying.
    Status: Fixed
  • Jul 16, 2009
    issue 126 (Generated comments should be compliant to StyleCop) Status changed by forever.zet   -   Fixed in 1.3.8
    Status: Fixed
    Fixed in 1.3.8
    Status: Fixed
 
Hosted by Google Code