Visual studio addin broken

384 views
Skip to first unread message

Edward Ned Harvey (ETO.Forms)

unread,
Dec 16, 2014, 5:14:30 PM12/16/14
to eto-...@googlegroups.com

The quick start guide recommends installing the visual studio addin, so I did.  I then restart VS, or don't (tried both ways), and when I go to new project (or new solution) and select an Eto.Forms template, I either get:

                Exception from HRESULT: 0x80041FE1

or

                The template specified cannot be found. Please check that the full path is correct.

 

I'm running on Visual Studio Pro 2013

curtis

unread,
Dec 16, 2014, 11:54:01 PM12/16/14
to eto-...@googlegroups.com
Hm, interesting. I've tried a few computers and haven't had any issues. Could you give me some more info to help troubleshoot this:

- Windows version?
- 32 or 64 bit?
- What VS2013 service pack do you have?

Cheers!
Curtis.

Rob....@ai-solutions.com

unread,
Jan 4, 2015, 11:00:44 AM1/4/15
to eto-...@googlegroups.com
I have the same issue:

VS2013 Premium Update 1
Windows 7 64-bit

Rob....@ai-solutions.com

unread,
Jan 4, 2015, 2:11:56 PM1/4/15
to eto-...@googlegroups.com, Rob....@ai-solutions.com
Installing update 4 for vs2013 fixed the issue

curtis

unread,
Jan 4, 2015, 2:56:29 PM1/4/15
to eto-...@googlegroups.com, Rob....@ai-solutions.com
Ah good to know!  I was just about to suggest that.

I'll see if I can make the addin require update 4 to prevent users from running into this in the future.

Cheers!
Curtis.

Rob....@ai-solutions.com

unread,
Jan 4, 2015, 3:48:00 PM1/4/15
to eto-...@googlegroups.com, Rob....@ai-solutions.com
To be clear, I don't know if update 4 is required...I just happened to install the latest.

curtis

unread,
Jan 4, 2015, 3:58:24 PM1/4/15
to eto-...@googlegroups.com, Rob....@ai-solutions.com
Hi Rob,

My guess is that it probably only requires update 3, but I will be recommending the latest update anyway as if any bugs arise it will be easier to support.  I've updated the quick start page to reflect this.

Thanks for helping flush this issue out! It is much appreciated.

Cheers!
Curtis.

Edward Ned Harvey (ETO.Forms)

unread,
Jan 13, 2015, 6:24:38 PM1/13/15
to eto-...@googlegroups.com
> From: eto-...@googlegroups.com [mailto:eto-...@googlegroups.com]
> On Behalf Of curtis
>
> My guess is that it probably only requires update 3, but I will be
> recommending the latest update anyway as if any bugs arise it will be easier
> to support.  I've updated the quick start page to reflect this.

Thanks for this, I confirmed that when I updated VS to Update4, it worked for me too.

However - I created a new project in VS, ran it with WinForms and WPF, then copied the directory over to mac where I have Xamarin Studio, and opened the sln in XS. When I try to run the mac app, it threw Eto.EtoException: Platform instance is null. Have you created your application?

Is that expected to work? I have also installed the Eto templates in Xamarin Studio, and I presume I can create a new project there (haven't tried yet), but doesn't it defeat the purpose? The whole point is to be able to code up a GUI in either platform, and expect it to behave reasonably when built & run on the other platform. Should I be doing something different?

Thanks again...

curtis

unread,
Jan 13, 2015, 9:10:41 PM1/13/15
to eto-...@googlegroups.com
Hi Edward,

If you want to run your app from Xamarin Studio, you will either have to use the templates provided, or create a monomac or xammac project as described here.  Unfortunately, VS templates must be valid in VS, so I cannot include those in the templates in the Visual Studio addin.

If you just want to run your app on OS X, but compile in VS, you can add the Eto.Platform.Mac.Template nuget. This will automatically create a <YourApp>.app bundle/folder in the output directory when you build, which you can zip up, transfer to a mac, unzip, then run.  Note that zipping/unzipping is important here, as otherwise the Launcher.exec file in the bundle won't get the executable bit set properly. You could also set the executable bit set manually after copying to mac as well, but I find the zip approach easier.

Hope this helps!
Curtis.

On Tuesday, January 13, 2015 at 3:24:38 PM UTC-8, Edward Ned Harvey wrote:

Edward Ned Harvey (ETO.Forms)

unread,
Jan 14, 2015, 6:49:15 AM1/14/15
to eto-...@googlegroups.com
> From: eto-...@googlegroups.com [mailto:eto-...@googlegroups.com]
> On Behalf Of curtis
>
> If you want to run your app from Xamarin Studio, you will either have to use
> the templates provided, or create a monomac or xammac project as
> described here.  Unfortunately, VS templates must be valid in VS, so I cannot
> include those in the templates in the Visual Studio addin.
>
> If you just want to run your app on OS X, but compile in VS, you can add the
> Eto.Platform.Mac.Template nuget. This will automatically create a
> <YourApp>.app bundle/folder in the output directory when you build, which
> you can zip up, transfer to a mac, unzip, then run.  Note that
> zipping/unzipping is important here, as otherwise the Launcher.exec file in
> the bundle won't get the executable bit set properly. You could also set the
> executable bit set manually after copying to mac as well, but I find the zip
> approach easier.

So what's the recommended way to put some code into git, share the same code across win/lin/mac, and have a pretty good reuse of code across all three?

I'm talking about a private git server, so it's ok to commit binaries, if that matters.

Thanks again...

curtis

unread,
Jan 14, 2015, 11:22:37 AM1/14/15
to eto-...@googlegroups.com
My recommendation, if you do not need to have any platform-specific code, is to use the "combined" project template.  This means you'd have three projects:

1) Library for all of your shared UI code.
2) Standard .exe project to build for Windows & Linux
3) MonoMac/XamMac app project to build for Mac

All of your shared UI code will lie in the library, so you'll have 100% code reuse.  #2 and #3 are just projects that launch the app.

Note that #3 is only needed if you either want to run/debug in Xamarin Studio on mac, or, you need to bundle mono (using a paid Xamarin.Mac subscription).

Hope this helps!
Curtis.


On Wednesday, January 14, 2015 at 3:49:15 AM UTC-8, Edward Ned Harvey wrote:
Reply all
Reply to author
Forward
0 new messages