There should be some error checking on the domain assembly lookup, to avoid "exploding", when running in some embed python dcc (in this case 3dsmax). This is what this pull request does.

The travis and appveyor CI builds are failing with this error:

assemblymanager.cs(70,37): error CS1056: Unexpected character `$'

Could you refactor so as not to use C# 6 features please? (only a small change, and easier than converting the project to C# 6 for now)

thanks,
Tony

Sure no problem.

A Qui, 7 de Jan de 2016, 09:21, Tony Roberts notifications@github.com
escreveu:

The travis and appveyor CI builds are failing with this error:

assemblymanager.cs(70,37): error CS1056: Unexpected character `$'

Could you refactor so as not to use C# 6 features please? (only a small
change, and easier than converting the project to C# 6 for now)

thanks,
Tony

—
Reply to this email directly or view it on GitHub
#114 (comment).

Failing on AppVeyor py26, but not due to code changes.

Sorry, I didn't notice before but this pull request is against the master branch. All pull requests need to be against the develop branch (which is merged into master prior to a release).

Ok, I will make one against the develop. Are you guys using simple git flow
workflow?

Tony Roberts notifications@github.com escreveu no dia quinta, 7/01/2016
às 19:47:

Sorry, I didn't notice before but this pull request is against the master
branch. all pull requests need to be agains the develop branch (which is
merged into master prior to a release).

—
Reply to this email directly or view it on GitHub
#114 (comment).

About as simple as it gets. The develop branch is for development; no problem accepting small commits directly on there, no need for a feature branch (although for more major features I would use a feature branch). Master is always buildable/releasable.

I'll move these commits to develop and create a new PR.

cheers,
Tony

If I haven't screwed anything up your changes should now be in #115 :)

Thanks ;).

Tony Roberts notifications@github.com escreveu no dia quinta, 7/01/2016
às 21:13:

If I haven't screwed anything up your changes should now be in #115
#115 :)

—
Reply to this email directly or view it on GitHub
#114 (comment).