ADO.NET Unit Testable Repository Generator

Commented Issue: Missing XML comment for publicly visible type or member... [1177]

icnocop — Fri, 26 Apr 2013 19:29:33 GMT

Hi.

Thank you for ADO.NET Unit Testable Repository Generator 0.5.

When I use Model.Types.tt to generate the classes from my edmx and build, I get lots of warnings that begin with:
warning CS1591: Missing XML comment for publicly visible type or member

I did some research and tried to add code similar to the following in those places where the warnings occur, but the Documentation property is always null.

```
if (!ReferenceEquals(entity.Documentation, null))
{
#>
/// <summary>
/// <#=entity.Documentation.Summary#> – <#=entity.Documentation.LongDescription#>
/// </summary>
<#
}
```

Any ideas?

Thank you.
Comments: ** Comment from web user: icnocop **

I went ahead and upload patch #14386 to resolve this issue.

Patch Uploaded: #14386

icnocop — Fri, 26 Apr 2013 19:28:54 GMT

icnocop has uploaded a patch.

Description:
Added missing XML comments for publicly visible type and members

Created Issue: Missing XML comment for publicly visible type or member... [1177]

icnocop — Fri, 26 Apr 2013 18:34:55 GMT

Closed Issue: Fix breaking code [95]

JohannesHoppe — Sat, 29 Dec 2012 12:11:22 GMT

Rohan Cragg reported breaking code on complex database scenarios.
 
We should find and fix this bug soon!

Comments:

no user feedback

Source code checked in, #20526

Project Collection Service Accounts — Mon, 01 Oct 2012 20:30:29 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #20525

Project Collection Service Accounts — Mon, 01 Oct 2012 20:28:33 GMT

Checked in by server upgrade

Created Issue: GetHashCode method problem with inherited entities [640]

martonrusko — Sat, 01 Oct 2011 13:09:39 GMT

I just tried the 0.5 version of the template. It's great.
I have found a bug in the generator code. It doesn’t care the parent entity's properties. GetHashCode method generates the hash code from the declaring type's properties. In inherited entities the identity property is found in the topmost base class. It skipped by the generator too.
The same problem causes the issue with the equality methods. There will be missing properties in inherited entities.
So, I modified the template and added the following method:
IEnumerable<EdmProperty> GetAllProperties(EntityType entityType, EdmType parentType = null)
{
IEnumerable<EdmProperty> result = new EdmProperty[0];
var propsType = parentType == null ? entityType : parentType;

if (propsType.BaseType != null)
result = GetAllProperties(entityType, propsType.BaseType);

result = result.Union(entityType.Properties.Where(p => p.DeclaringType == propsType));
return result;
}

Also replaced the foreach methods at the following line numbers:
253, 316, 332:
original: foreach(EdmProperty edmProperty in entity.Properties.Where(p => p.DeclaringType == entity))

replaced: foreach(EdmProperty edmProperty in GetAllProperties(entity))

Created Issue: EntitiesMock.ObjectSet.cs fails with AddObject [357]

djryan7 — Mon, 02 May 2011 01:35:55 GMT

First I would like to say what great tool for use with the EF. However my first test fails in AddObject(T entity) when I try to add a new single entity to the Repository. I have an entity with the following fields, however the primary key is a composite key of the TAG_AGENCY_ID, and TAG_SERIAL_NUMBER. When I try to add the entity the HasIdProperty returns true and try's to autogenerate a key. However since there are 2 fields in the set that contain ID is the name it trys to auto-generate. Wouldn't it be better to assume that if the entity being passed contained all the key values that made up the composite key that it would try to auto-generate. Of course I can change the code manually but if I regenerate from entity changes I'm broken.

[System.CodeDom.Compiler.GeneratedCode("ADO.NET Unit Testable Repository Generator", "0.5")]
public partial class TRANSPONDER_STATUS
{
public virtual decimal TAG_AGENCY_ID
public virtual decimal TAG_SERIAL_NUMBER
public virtual Nullable<decimal> FILE_ID
public virtual Nullable<decimal> TAG_VALID

Commented Issue: Implement On Property Change for POCO [258]

apocolpse — Sat, 09 Apr 2011 14:06:02 GMT

Implement the on property change pattern for scalar entities
Comments: ** Comment from web user: apocolpse **

http://msdn.microsoft.com/en-us/library/system.componentmodel.inotifypropertychanged.aspx

Commented Issue: Implement On Property Change for POCO [258]

apocolpse — Wed, 06 Apr 2011 20:23:09 GMT

Implement the on property change pattern for scalar entities
Comments: ** Comment from web user: apocolpse **

I'm proposing something like this property declaration
public partial class Category {
public global::System.Int32 CategoryID
{
get
{
return _CategoryID;
}
set
{
if (_CategoryID != value)
{
OnCategoryIDChanging(value);
_CategoryID = value;
OnCategoryIDChanged();
}
}
}

private global::System.Int32 _CategoryID;
partial void OnCategoryIDChanging(global::System.Int32 value);
partial void OnCategoryIDChanged();
}

New Post: Feature Wishlist

andiih — Tue, 05 Apr 2011 08:14:36 GMT

At the time of writing I was looking for something to auto-generate my repo's. The ef4templates link works, but I didn't want/need STE's. I've "Settled" on http://efrepository.codeplex.com/ which gives me Add, Where, Delete for a given entity, and a Unit Of Work with Commit - which (just) covers the basics. A Get(var PK) would be useful, but not necessary as I can do it with Where, but it would save a couple of expressions :-) I've built new projects AND reverse engineered old ones into this Repo architecture. I really like the "codeless" class approach - all done with inheritance.

As for Anemic v DDD: I can create buddy classes to extend the functionality of my entities, or I can package them off As-Is into other layers, so I don't think this approach really forces as decision either way.

Perhaps I shouldn't have said "Full Repository Generator" - perhaps "Really Really Basic Building Blocks Repo Auto-Generator" would have been closer to the mark!

New Post: Creating Repositories

photo_tom — Mon, 04 Apr 2011 23:52:05 GMT

I resolved the problem. It was a case of my not understanding completely as to how it works.

I made one modification to the template though. We use stylecop, so I added all of the comments that it expects into the template.

There is one thing you may want to consider adding to template. I manually created a singleton class (see below) to handle instancing the repository. By doing it this way, I hide all details about how to construct a repository. I did it as a Singleton because of how the connection string was passed in. But it does work fairly well this way.

Overall, this template is now a standard part of my projects. An excellent piece of code.

Thanks

Tom

        /// <summary>
        /// Private backing field for DayScheduleRepository.
        /// </summary>
        private static DayScheduleRepository privateDayScheduleRepository;

        /// <summary>
        /// Gets  DayScheduleRepository .
        /// </summary>
        public static DayScheduleRepository DayScheduleRepository
        {
            get
            {
                if (null == privateDayScheduleRepository)
                {
                    //Logger.Info("Creating Repository for DayScheduleRepository");
                    privateDayScheduleRepository = new DayScheduleRepository(new EfRepository<DaySchedule>() as IRepository<DaySchedule>, UnitOfWork);
                }

                return privateDayScheduleRepository;
            }
        }

        private static EfUnitOfWork unitOfWork;

        /// <summary>
        /// The unit of work.  This is the overall device context for the system.
        /// </summary>
        public static EfUnitOfWork UnitOfWork
        {
            get
            {
                if (unitOfWork == null)
                {
                   unitOfWork = new EfUnitOfWork();
                }
                return unitOfWork;
            }
            private set
            {
                unitOfWork = value;
            }
        }

        #region Methods

        /// <summary>
        /// The constructor helper.
        /// </summary>
        /// <param name="newDatabase">
        /// The new database.
        /// </param>
        private static void ConstructorHelper(string newDatabase)
        {
            string database2Open = string.IsNullOrEmpty(newDatabase) ? "VisServer" : newDatabase;
            string connectionString = ConnectiionString.GetSqlConnectionString(".\\sqlexpress", database2Open);
           // Logger.Info("Initialized database", Logger.VarName(() => database2Open));
            UnitOfWork = new EfUnitOfWork(connectionString);
            //Logger.Info("Database Context <EfUnitOfWork> Created");
        }

        #endregion
    }

New Post: Feature Wishlist

JohannesHoppe — Mon, 04 Apr 2011 23:12:14 GMT

@andiih

Wow, a full repository generator is some kind of the Holy Grail. There are so many ways of implementing even the basic CRUD operations. I’m sure that everybody expects something different from his repositories. (e.g. anemic vs. DDD)

On case that you already researched on that topic, I would suggest that you share your ideas or your current implementation of a “generic” repository. I’m open for every type of implementation!!

New Post: Feature Wishlist

JohannesHoppe — Mon, 04 Apr 2011 23:02:39 GMT

Thanks for the feedback.

@utcyclist
Currently I’m not happy to define preprocessor definitions (DO_NOT_USE_UNITY and DO_NOT_INCLUDE_ EQUALITY_MEMBERS) for making switches. This makes more features difficulty to implement, since I can’t build a T4 template that fits to every requirement by default.

Solution A)
It would be much better to have any kind of graphical wizard to choose between different options that affect the T4 template and the generated code. Unfortunately my current projects to not include relational databases at all. So I have only spare time to research on that topic.

But if anybody could provide me with a feature toggle for T4 templates I could include feature request in a straightforward way.

Solution B)
Manual editing of the T4 template afterwards. Would this be acceptable, too?!

By the way:
I encourage everybody to submit patches or to request more rights to the SVN repository. I’m very open to include your suggestions to the project. (But time is rare, as always! ;-)

New Post: Creating Repositories

JohannesHoppe — Mon, 04 Apr 2011 22:44:41 GMT

I'm not sure if I understand your problem correctly.

Do you
a) have problems to use the repo generator?
b) or does the T4 templates do not generate all required files?

Commented Issue: Fix breaking code [95]

JohannesHoppe — Mon, 04 Apr 2011 22:41:29 GMT

Rohan Cragg reported breaking code on complex database scenarios.

We should find and fix this bug soon!
Comments: ** Comment from web user: JohannesHoppe **

Has anybody the same issues?! (not building code)

Commented Issue: Implement On Property Change for POCO [258]

JohannesHoppe — Mon, 04 Apr 2011 22:40:33 GMT

Implement the on property change pattern for scalar entities
Comments: ** Comment from web user: JohannesHoppe **

Could you provide a code example, please?!

New Post: Feature Wishlist

utcyclist — Mon, 04 Apr 2011 22:15:50 GMT

The MockObjectSet<T>.AutoIncrementIdProperty() method assumes that my Id fields are of type int. In our environment we have many Id fields which are guids (or even worse, strings). It would be nice if this were modified to handle Id properties of different types.

It would also be useful to be able to disable the autoincrement altogether for cases when it's not desired.

Commented Issue: Implement On Property Change for POCO [258]

apocolpse — Fri, 01 Apr 2011 20:42:42 GMT

Implement the on property change pattern for scalar entities
Comments: ** Comment from web user: apocolpse **

or at least make them optional

Created Issue: Implement On Property Change for POCO [258]

apocolpse — Fri, 01 Apr 2011 16:12:04 GMT

Implement the on property change pattern for scalar entities