Skip to content
This repository has been archived by the owner on Jan 16, 2024. It is now read-only.

VS2017 Crash #38

Closed
dcastenholz opened this issue Nov 27, 2018 · 7 comments
Closed

VS2017 Crash #38

dcastenholz opened this issue Nov 27, 2018 · 7 comments
Labels
bug Confirmed bug workaround available There's a problem that needs fixed, but a procedure can currently be used to get the same result

Comments

@dcastenholz
Copy link
Contributor

Created a simple model with 2 entities and a 1 to many association. Selecting either entity and then selecting the Association Sources (or Targets) entry and then clicking on the Properties window dropdown for 'End2 Multiplicity' (which is currently set to 'ZeroMany') causes VS2017 to crash.

@dcastenholz
Copy link
Contributor Author

Just realized that this is a duplicate of #34.

@msawczyn
Copy link
Owner

Can you make it happen again and upload a VS log? I can't replicate it. :-(

@msawczyn msawczyn added need info Need more information to track this down duplicate Duplicate issue labels Nov 28, 2018
@dcastenholz
Copy link
Contributor Author

Didn't get much, but it does tell where the exception is generated.

<entry>
    <record>644</record>
    <time>2018/11/28 21:13:13.500</time>
    <type>Information</type>
    <source>ExtensionCrashNotification</source>
    <description>c:\program files (x86)\microsoft visual studio\2017\enterprise\common7\ide\extensions\e3baosf2.zpy\Sawczyn.EFDesigner.EFModel.Dsl.dll!Sawczyn.EFDesigner.EFModel.TargetMultiplicityTypeConverter.GetStandardValues</description>
  </entry>

@msawczyn msawczyn added bug Confirmed bug and removed need info Need more information to track this down duplicate Duplicate issue labels Nov 29, 2018
@msawczyn
Copy link
Owner

Found the problem and will get it fixed quite soon.

The workaround is to make sure the association line has focus rather than the class.

Thanks for this info!

@msawczyn msawczyn added the workaround available There's a problem that needs fixed, but a procedure can currently be used to get the same result label Nov 29, 2018
msawczyn added a commit that referenced this issue Nov 30, 2018
…s were changed under certain conditions (See #38)
@msawczyn
Copy link
Owner

@ddewaleffe and @dcastenholz ,

I've put a fix in and published as a pre-release version (v1.2.6.19-pre) at https://github.com/msawczyn/EFDesigner/releases/tag/v1.2.6.19-pre

If you could give it a try I'd appreciate it.

@ddewaleffe
Copy link

I did try v1.2.6.19 on the multiplicity change that was causing a crash. The fix appears to work.

@msawczyn
Copy link
Owner

msawczyn commented Dec 1, 2018

Super. I'll close the issue and release that build. Thanks!

@msawczyn msawczyn closed this as completed Dec 1, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Confirmed bug workaround available There's a problem that needs fixed, but a procedure can currently be used to get the same result
Projects
None yet
Development

No branches or pull requests

3 participants