karvonite Work Item Rss Feed

CLOSED FEATURE: New Persistence Model Editor

DiegoHernanCanepa — Wed, 18 Nov 2009 02:20:35 GMT

We've a new Persistence Model Editor in the oven (former Persistence Model Designer). The new version will be released as part of the December 2009 release. A beta version just for testing and feedback purposes might be released soon.

*Here is a list of the new features:*

* New Name: Persistence Model Editor (former Persistence Model Designer).
* New UI experience. We've a new look and feel: simpler and more intuitive. Less is more.
* Improved Undo/Redo system.
* Quickly find model elements using the new search box.
* The new Add Types and Members functionality lets you add element faster. No more right clicks, no more Batch Add.
* Errors can be easily visualized in the tree view. An automatic error list shows or hide as model changes.
* Multiplatform support. Now you can choose several platforms (Windows, .NET CF and Xbox360) and maintain just one model file.
* Model navigation.

CREATED FEATURE: New Persistence Model Editor

DiegoHernanCanepa — Tue, 17 Nov 2009 23:44:54 GMT

CLOSED FEATURE: Multiplatform compatibility for persistence models

DiegoHernanCanepa — Fri, 14 Aug 2009 03:55:31 GMT

When you create a persistence model, selected types are stored using the qualified assembly name which includes the assembly version and the publickey if it is strong signed. This might cause a problem in situations where your persistence model will be used in two different platforms. For example Windows and XBox platform. The workaround is quite simple, but tedious.

We're working on some new stuff for the next release. This situation will be automatically resolved bye the Karvonite framework allowing you to use the same persistence model in many platforms.

EDITED FEATURE: Multiplatform compatibility for persistence models

DiegoHernanCanepa — Fri, 14 Aug 2009 03:54:37 GMT

CREATED FEATURE: Multiplatform compatibility for persistence models

DiegoHernanCanepa — Wed, 12 Aug 2009 22:14:34 GMT

When you create a persistence model, selected types are stored using the qualified assembly name which includes the assembly version and the publickey if it is strong signed. This might cause a problem in situations where your persistence model will be used in two different platforms. For example Windows and XBox platform. The solution is simple. Just create two different models, but this is a bit annoying.

We're working on some new stuff for the next release. This situation will be automatically resolved bye the Karvonite framework allowing you to use the same persistence model in many platforms.

CLOSED ISSUE: Updated exception messages for fields and properties

DiegoHernanCanepa — Thu, 30 Jul 2009 18:27:35 GMT

Some exception messages were updated to report containing type.

CREATED ISSUE: Updated exception messages for fields and properties

DiegoHernanCanepa — Thu, 30 Jul 2009 18:27:27 GMT

Some exception messages were updated to report containing type.

CLOSED FEATURE: Improved Object Library Format

DiegoHernanCanepa — Thu, 30 Jul 2009 18:24:19 GMT

The internal format of the object library storage has been updated providing better performance and reduced memory use.

CLOSED ISSUE: ModelException raised for protected properties

DiegoHernanCanepa — Thu, 30 Jul 2009 18:22:32 GMT

Karvonite throws ModelException when for properties (fields work fine) with protected visibility.

EDITED ISSUE: ModelException raised for protected properties

DiegoHernanCanepa — Thu, 30 Jul 2009 18:22:16 GMT

Karvonite throws ModelException when for properties (fields work fine) with protected visibility.

CREATED ISSUE: ModelException raised for protected properties

DiegoHernanCanepa — Thu, 30 Jul 2009 18:17:06 GMT

Karvonite throws ModelException when for properties (fields work fine) with protected visibility.

COMMENTED ISSUE: Better Exception Messages

JeReT — Wed, 29 Jul 2009 18:55:42 GMT

Hi,
When i load an object model, there where some exceptions like "The property X couldn't be found". It would be much more helpful when you see the location of the Variable (like: My.Namespace.MyClass.X).

Same for a NullReferenceException which is raised when i try to save. The message i got is something like: "The value must not be NULL. parameter name: key"
I think some value inside of the program which has to be saved is null. But with this message i have no idea where to start searching.
Comments: When calling objectSpace.Save();

COMMENTED ISSUE: Better Exception Messages

DiegoHernanCanepa — Wed, 29 Jul 2009 17:28:55 GMT

CREATED ISSUE: Better Exception Messages

JeReT — Wed, 29 Jul 2009 11:09:36 GMT

COMMENTED ISSUE: Renamed Assemblies can't be found

DiegoHernanCanepa — Fri, 24 Jul 2009 19:32:33 GMT

Hi,
when i renamed the assembly name of my start-project and tried to use it with the persistence model designer, it couldn't be found. even if i correct the path.
Comments: This is strange. Could you provide some additional info.

CREATED ISSUE: Renamed Assemblies can't be found

JeReT — Fri, 24 Jul 2009 17:52:59 GMT

Hi,
when i renamed the assembly name of my start-project and tried to use it with the persistence model designer, it couldn't be found. even if i correct the path.

COMMENTED ISSUE: Problem with resolving references

JeReT — Fri, 17 Jul 2009 08:28:21 GMT

COMMENTED ISSUE: Problem with resolving references

DiegoCanepa — Thu, 16 Jul 2009 15:28:28 GMT

COMMENTED ISSUE: Problem with resolving references

JeReT — Wed, 15 Jul 2009 17:30:23 GMT

Hi,
I am wondering why this Issue is closed: http://code.msdn.microsoft.com/karvonite/WorkItem/View.aspx?WorkItemId=45
It doesn't seem to me that the problem has been fixed (or is there a fix within the July 2009 release?).

My problem is something like this:
I loaded an .exe assembly into the Persistence Model Designer.
It references assembly A, B, C and X (and some others).
It can't resolve A, B, and C references. The reference to X is ok.
Then I also added those assemblies to the model designer and got the following problems:
- 'A' can not resolve a System Assembly and can not resolve X (it has also a reference to X)
- 'B' can not resolve X (it has also a reference to X)
- 'C' has no problems at all
- 'X' also has no problems.

when I compiled my .exe as a .dll and added it to the persistence model designer, 'C' doesn't make problems any more.
All assemblies are compiled from the same .sln and into the same directory.

I really hope there is a solution for this or it is a bug which is solved in the next release.
Please help.
Comments: Hi DiegoCanepa, i just tried to rebuild my problem by copying all projects and removing the content from it. when i don't use any datatype of one referenced assembly, the reference will be optimized away... so there are not all references inside of Test.A.dll as in the original project. Ok, i don't want to talk too much: the result is not the same as in the original assemblies but there are other resolving problems. maybe these are similar to the original... Or they are only existing because i used the AssemblyMapper.dll which you posted here... however... take a look and let me know when you found something. thanks, JeReT

COMMENTED ISSUE: Problem with resolving references

DiegoCanepa — Tue, 14 Jul 2009 14:54:28 GMT

Hi,
I am wondering why this Issue is closed: http://code.msdn.microsoft.com/karvonite/WorkItem/View.aspx?WorkItemId=45
It doesn't seem to me that the problem has been fixed (or is there a fix within the July 2009 release?).

My problem is something like this:
I loaded an .exe assembly into the Persistence Model Designer.
It references assembly A, B, C and X (and some others).
It can't resolve A, B, and C references. The reference to X is ok.
Then I also added those assemblies to the model designer and got the following problems:
- 'A' can not resolve a System Assembly and can not resolve X (it has also a reference to X)
- 'B' can not resolve X (it has also a reference to X)
- 'C' has no problems at all
- 'X' also has no problems.

when I compiled my .exe as a .dll and added it to the persistence model designer, 'C' doesn't make problems any more.
All assemblies are compiled from the same .sln and into the same directory.

I really hope there is a solution for this or it is a bug which is solved in the next release.
Please help.
Comments: Try this fixed AssemblyMapper.dll. I'll post it in the download section once you test it. Regards and thanks for reporting the error. Diego