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

Earlier this year

  • Nov 21, 2009
    issue 23 (ReSharper 5.0 support) commented on by shanecourtrille   -   Not sure how to mark this as an enhancement.
    Not sure how to mark this as an enhancement.
  • Nov 21, 2009
    issue 23 (ReSharper 5.0 support) reported by shanecourtrille   -   A ReSharper 5.0 version would be helpful.
    A ReSharper 5.0 version would be helpful.
  • Aug 31, 2009
    r40 (Some compile-errors removed) committed by mellekoning   -   Some compile-errors removed
    Some compile-errors removed
  • Aug 31, 2009
    r39 (Some compile-errors removed) committed by mellekoning   -   Some compile-errors removed
    Some compile-errors removed
  • Aug 31, 2009
    r38 (Resharper 4.5 branch added) committed by mellekoning   -   Resharper 4.5 branch added
    Resharper 4.5 branch added
  • Aug 31, 2009
    r37 (testing) committed by mellekoning   -   testing
    testing
  • Aug 31, 2009
    r36 (Resharper 4.5 branch added) committed by mellekoning   -   Resharper 4.5 branch added
    Resharper 4.5 branch added
  • Jul 07, 2009
    r35 (Patch from Melle Koning applied to prevent null ref exceptio...) committed by stefan.lieser   -   Patch from Melle Koning applied to prevent null ref exception
    Patch from Melle Koning applied to prevent null ref exception

Older

  • Nov 21, 2008
    issue 20 (Type 'YesNo' could not be resolved.) Status changed by slie...@lieser-online.de   -   Fixed in upcoming release 0.9.5
    Status: Fixed
    Fixed in upcoming release 0.9.5
    Status: Fixed
  • Nov 21, 2008
    r34 (- Testcases added for boolean (YesNo, TrueFalse), Binary, An...) committed by slie...@lieser-online.de   -   - Testcases added for boolean (YesNo, TrueFalse), Binary, AnsiString - Code Style embedded - NHibernate added
    - Testcases added for boolean (YesNo, TrueFalse), Binary, AnsiString - Code Style embedded - NHibernate added
  • Nov 21, 2008
    r33 (Array types added to parser) committed by slie...@lieser-online.de   -   Array types added to parser
    Array types added to parser
  • Nov 21, 2008
    r32 (Bugfix in scanner while scanning white space) committed by slie...@lieser-online.de   -   Bugfix in scanner while scanning white space
    Bugfix in scanner while scanning white space
  • Nov 21, 2008
    r31 (- Refactoring Parser - Output Assembly name changed to repro...) committed by slie...@lieser-online.de   -   - Refactoring Parser - Output Assembly name changed to reproduce former bug
    - Refactoring Parser - Output Assembly name changed to reproduce former bug
  • Nov 21, 2008
    issue 10 (Wrong highlighting with error message if project name does n...) Status changed by slie...@lieser-online.de   -   Fixed in upcoming release 0.9.5
    Status: Fixed
    Fixed in upcoming release 0.9.5
    Status: Fixed
  • Nov 21, 2008
    r30 (Assemblynames added to parser) committed by slie...@lieser-online.de   -   Assemblynames added to parser
    Assemblynames added to parser
  • Nov 21, 2008
    issue 19 (Mapping analysis: Unresolved <T> in concrete type) Status changed by slie...@lieser-online.de   -   Not easy to fix because the mapped class type is generic. Type parameter T must be compared to type="Guid".
    Status: Accepted
    Not easy to fix because the mapped class type is generic. Type parameter T must be compared to type="Guid".
    Status: Accepted
  • Nov 21, 2008
    issue 17 (IUserType mapped properties shown as incorrect) Status changed by slie...@lieser-online.de   -  
    Status: Accepted
    Status: Accepted
  • Nov 21, 2008
    issue 21 (Improvement navigate and check proxy attribute) changed by slie...@lieser-online.de   -  
    Status: Accepted
    Labels: Type-Enhancement Type-Defect
    Status: Accepted
    Labels: Type-Enhancement Type-Defect
  • Nov 21, 2008
    issue 18 (NHibernate build in type is not resolved) changed by slie...@lieser-online.de   -  
    Status: Duplicate
    Status: Duplicate
  • Nov 21, 2008
    issue 20 (Type 'YesNo' could not be resolved.) commented on by slie...@lieser-online.de   -   Issue 18 has been merged into this issue.
    Issue 18 has been merged into this issue.
  • Nov 21, 2008
    issue 18 (NHibernate build in type is not resolved) Status changed by slie...@lieser-online.de   -  
    Status: Accepted
    Status: Accepted
  • Nov 21, 2008
    issue 10 (Wrong highlighting with error message if project name does n...) Status changed by slie...@lieser-online.de   -  
    Status: Accepted
    Status: Accepted
  • Nov 21, 2008
    issue 20 (Type 'YesNo' could not be resolved.) Status changed by slie...@lieser-online.de   -  
    Status: Accepted
    Status: Accepted
  • Nov 21, 2008
    issue 15 (Take into account the assembly-name instead of project-name) changed by slie...@lieser-online.de   -   Duplicate item
    Status: Duplicate
    Duplicate item
    Status: Duplicate
  • Nov 21, 2008
    issue 10 (Wrong highlighting with error message if project name does n...) commented on by slie...@lieser-online.de   -   Issue 15 has been merged into this issue.
    Issue 15 has been merged into this issue.
  • Nov 20, 2008
    r29 (Scanner doesn't throw exception on unknown character now) committed by slie...@lieser-online.de   -   Scanner doesn't throw exception on unknown character now
    Scanner doesn't throw exception on unknown character now
  • Nov 19, 2008
    r28 (Error handling added to parser) committed by slie...@lieser-online.de   -   Error handling added to parser
    Error handling added to parser
  • Nov 18, 2008
    r27 (Parser for generic types fixed) committed by slie...@lieser-online.de   -   Parser for generic types fixed
    Parser for generic types fixed
  • Nov 18, 2008
    r26 (Parser for generic types fixed) committed by slie...@lieser-online.de   -   Parser for generic types fixed
    Parser for generic types fixed
  • Nov 18, 2008
    r25 (Unneeded files deleted) committed by slie...@lieser-online.de   -   Unneeded files deleted
    Unneeded files deleted
  • Nov 18, 2008
    r24 (Project repaired after svn problems) committed by slie...@lieser-online.de   -   Project repaired after svn problems
    Project repaired after svn problems
  • Nov 18, 2008
    r23 (Parser for generic type names added ) committed by slie...@lieser-online.de   -   Parser for generic type names added
    Parser for generic type names added
  • Nov 18, 2008
    r22 (Scanner for generic type names added) committed by slie...@lieser-online.de   -   Scanner for generic type names added
    Scanner for generic type names added
  • Nov 15, 2008
    Features (What features are available for .hbm.xml mapping files?) Wiki page added by slie...@lieser-online.de
  • Oct 20, 2008
    issue 22 (Does not work with Resharper 4.1) Status changed by slie...@lieser-online.de   -   See the download section, there is build 0.9.4
    Status: Done
    See the download section, there is build 0.9.4
    Status: Done
  • Oct 20, 2008
    issue 22 (Does not work with Resharper 4.1) commented on by scott.w.white   -   Correction: I fetched the latest from SVN and compiled with my version of Resharper and all works. Perhaps new Bins should be provided? I can provide this if needed. Let me know. Thanks
    Correction: I fetched the latest from SVN and compiled with my version of Resharper and all works. Perhaps new Bins should be provided? I can provide this if needed. Let me know. Thanks
  • Oct 20, 2008
    issue 22 (Does not work with Resharper 4.1) reported by scott.w.white   -   What steps will reproduce the problem? 1. Install Resharper 4.1 2. Run copy-plugin.cmd 3. Files are not copied because directory is hard coded Patched file to use directory with 4.1 1. Launch VS.Net 2. Open any .hbm.xml file The attached exception occurs. Version: 0.0.9.2 of NH Plugin
    What steps will reproduce the problem? 1. Install Resharper 4.1 2. Run copy-plugin.cmd 3. Files are not copied because directory is hard coded Patched file to use directory with 4.1 1. Launch VS.Net 2. Open any .hbm.xml file The attached exception occurs. Version: 0.0.9.2 of NH Plugin
  • Oct 12, 2008
    issue 21 (Improvement navigate and check proxy attribute) reported by gustavo.ringel   -   I defined in a class the following <class name="LoteServicio" table="LotesServicios" proxy="ILoteServicio"> The plugin does not check if ILoteServicio exists and does not navigate to it... I don't know how difficult it is, but it will be nice to have this check also.
    I defined in a class the following <class name="LoteServicio" table="LotesServicios" proxy="ILoteServicio"> The plugin does not check if ILoteServicio exists and does not navigate to it... I don't know how difficult it is, but it will be nice to have this check also.
  • Oct 09, 2008
    issue 20 (Type 'YesNo' could not be resolved.) reported by dmdavis.net   -   To reproduce: 1. Create a mapping to a boolean property. 2. Set the type to YesNo (a char(1) column with Y for true and N for false). 3. Notice the red squiggle under type="YesNo" 4. Compile The mapping compiles and creates the schema just fine, but nhplugin doesn't recognize YesNo as a valid type. I get the same issue with TrueFalse, as well. http://www.hibernate.org/hib_docs/nhibernate/html/mapping.html#mapping-types-basictypes
    To reproduce: 1. Create a mapping to a boolean property. 2. Set the type to YesNo (a char(1) column with Y for true and N for false). 3. Notice the red squiggle under type="YesNo" 4. Compile The mapping compiles and creates the schema just fine, but nhplugin doesn't recognize YesNo as a valid type. I get the same issue with TrueFalse, as well. http://www.hibernate.org/hib_docs/nhibernate/html/mapping.html#mapping-types-basictypes
  • Oct 05, 2008
    issue 19 (Mapping analysis: Unresolved <T> in concrete type) reported by mtb.snowboard   -   What steps will reproduce the problem? 1. define public interface IEntity<T> { T ID { get; } } abstract public class BaseEntity<T> : IEntity<T> { private T _id; public virtual T ID { get { return _id; } protected set { _id = value; } } } public abstract class VersionedBaseEntity<T> : BaseEntity<T> { private int _version; public virtual int Version { get { return _version; } } } public abstract class BaseAPPEntity : VersionedBaseEntity<Guid> { } public partial class MyEntity: BaseAPPEntity { public virtual string Name { get; set; } public MyEntity() { } } Mapping: <id name="ID" column="ID" type="Guid" access="field.lowercase-underscore"> <generator class="guid.comb"/> </id> What is the expected output? What do you see instead? Expected -> no warning I see: Class name 'Guid' should be 'T' or a descendant for field '_id' What version of the product are you using? On what operating system? 0.0.9.4 Please provide any additional information below. Just downloaded latest trunk (version 20) and debugged. The problem is in Analysis\MappingFile\MappingFileAnalysisElementProcessor.cs: 446. R# says that fieldtype is T instead of Guid. I don't know how this works (first time i see r# api), just tried a quickwatch to see if there are some other property with 'Guid' type but i haven't found. So i dont' know if the problem is in r# or in your code, the standard r# analysis worked fine.
    What steps will reproduce the problem? 1. define public interface IEntity<T> { T ID { get; } } abstract public class BaseEntity<T> : IEntity<T> { private T _id; public virtual T ID { get { return _id; } protected set { _id = value; } } } public abstract class VersionedBaseEntity<T> : BaseEntity<T> { private int _version; public virtual int Version { get { return _version; } } } public abstract class BaseAPPEntity : VersionedBaseEntity<Guid> { } public partial class MyEntity: BaseAPPEntity { public virtual string Name { get; set; } public MyEntity() { } } Mapping: <id name="ID" column="ID" type="Guid" access="field.lowercase-underscore"> <generator class="guid.comb"/> </id> What is the expected output? What do you see instead? Expected -> no warning I see: Class name 'Guid' should be 'T' or a descendant for field '_id' What version of the product are you using? On what operating system? 0.0.9.4 Please provide any additional information below. Just downloaded latest trunk (version 20) and debugged. The problem is in Analysis\MappingFile\MappingFileAnalysisElementProcessor.cs: 446. R# says that fieldtype is T instead of Guid. I don't know how this works (first time i see r# api), just tried a quickwatch to see if there are some other property with 'Guid' type but i haven't found. So i dont' know if the problem is in r# or in your code, the standard r# analysis worked fine.
  • Sep 30, 2008
    issue 18 (NHibernate build in type is not resolved) reported by Michal.Liwoj   -   <property name="XmlData" type="StringClob"> <column name="XmlData" length="1073741823" sql-type="ntext" not-null="true"/> </property> Error: 'Type StringClob could not be resolved' Plugin version 0.0.9.4 @ R$ 4.1 @ VS 9.0 SP1 NHibernate 1.0.4. StringClobType is defined in namespace NHibernate.Type
    <property name="XmlData" type="StringClob"> <column name="XmlData" length="1073741823" sql-type="ntext" not-null="true"/> </property> Error: 'Type StringClob could not be resolved' Plugin version 0.0.9.4 @ R$ 4.1 @ VS 9.0 SP1 NHibernate 1.0.4. StringClobType is defined in namespace NHibernate.Type
  • Sep 23, 2008
    issue 17 (IUserType mapped properties shown as incorrect) reported by will.shaver   -   What steps will reproduce the problem? 1. Create an IUserType class to implement a custom type. For example: http://www.lostechies.com/blogs/rhouston/archive/2008/03/23/mapping- strings-to-booleans-using-nhibernate-s-iusertype.aspx 2. Add the user type to your mapping: <property name="Descr" type="Framework.LegacyStringUserType, Framework"/> 3. Add the actual type to your class class Product { public string Descr { get;set;} } 4. It will show as an error "class name LegacyStringUserType should be string or a descendant for getter property" What is the expected output? What do you see instead? No Error What version of the product are you using? On what operating system? 0.0.9.4 / Resharper 4.1 Please provide any additional information below. Thanks for the awesome plugin...
    What steps will reproduce the problem? 1. Create an IUserType class to implement a custom type. For example: http://www.lostechies.com/blogs/rhouston/archive/2008/03/23/mapping- strings-to-booleans-using-nhibernate-s-iusertype.aspx 2. Add the user type to your mapping: <property name="Descr" type="Framework.LegacyStringUserType, Framework"/> 3. Add the actual type to your class class Product { public string Descr { get;set;} } 4. It will show as an error "class name LegacyStringUserType should be string or a descendant for getter property" What is the expected output? What do you see instead? No Error What version of the product are you using? On what operating system? 0.0.9.4 / Resharper 4.1 Please provide any additional information below. Thanks for the awesome plugin...
  • Sep 21, 2008
    issue 14 (Properties without setters still marked as an error, even wi...) Status changed by slie...@lieser-online.de   -   Fixed with 0.9.4
    Status: Fixed
    Fixed with 0.9.4
    Status: Fixed
  • Sep 21, 2008
    issue 8 (type is being remarked as error) Status changed by slie...@lieser-online.de   -  
    Status: Fixed
    Status: Fixed
  • Sep 21, 2008
    issue 12 (When using a component every component property is navigatab...) Status changed by slie...@lieser-online.de   -  
    Status: Fixed
    Status: Fixed
  • Sep 21, 2008
    issue 8 (type is being remarked as error) commented on by gustavo.ringel   -   Types are working ok, as far as i checked in 0.0.9.4
    Types are working ok, as far as i checked in 0.0.9.4
  • Sep 21, 2008
    issue 12 (When using a component every component property is navigatab...) commented on by gustavo.ringel   -   Tested my report in 0.0.9.4 and it is working ok! You can close it!
    Tested my report in 0.0.9.4 and it is working ok! You can close it!
  • Sep 21, 2008
    issue 16 (NHPlugin broken for v4.1) Status changed by slie...@lieser-online.de   -   Hi Gustavo, you are right. I just downloaded build 0.9.4 that runs with ReSharper 4.1. Cheers, Stefan Lieser
    Status: Fixed
    Hi Gustavo, you are right. I just downloaded build 0.9.4 that runs with ReSharper 4.1. Cheers, Stefan Lieser
    Status: Fixed
  • Sep 21, 2008
    r20 (Batch added to remove the plugin) committed by slie...@lieser-online.de   -   Batch added to remove the plugin
    Batch added to remove the plugin
  • Sep 21, 2008
    issue 16 (NHPlugin broken for v4.1) reported by gustavo.ringel   -   I configured the NHPlugin for vs4.1 and every time i try to enter to an XML mapping i get Resharper expection with a MethodMissingException. Removing the plugin stopped the exception.
    I configured the NHPlugin for vs4.1 and every time i try to enter to an XML mapping i get Resharper expection with a MethodMissingException. Removing the plugin stopped the exception.
 
Hosted by Google Code