-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception when using in VS2015... #26
Comments
Can you please try the latest version 0.6.1.8? Hi, While pulling from NuGet I get the following exceptionj. Same occurrs if I Severity Code Description Project File Line Suppression State — |
The template stuff is still badly broken even in the latest 0.6.1.9 packages - definitely for VS2015, and probably for other versions of VS too, given the nature of the problem. Brand new VS2015 console app project, add the docopt package, and it will immediately fail as it tries to build post-install:
The pathing is correct - the problem seems to simply be that, at the point that the template transform attempts to run, If it was using the actual package path, it would presumably work. It seems like it used to use the package path - natiki's initial report shows error output that is indeed using the packaged path, and it seems to have been failing due to a simple typo which omits a necessary slash between the dir and the DLL name:
Not sure what happened here - seems like the original problem that this issue described was a simple fix, but instead (or for separate reasons afterward?) things got switched up to use the project output path - which is always going to fail for any project which doesn't already have |
Need to look into this again |
Happy to help test any changes (on VS2015 and VS2013). I know that public package maintenance is no dev's idea of a good time, but I think it's worth considering whether the T4 templating stuff should maybe be spun off into a separate nuget package. Automatic generation of strongly-typed config classes is great if you want or need it, but Docopt is quite useful without out; others who've been hoping to see it made available in the form of a single It right away struck me as a bit odd that a lib that's otherwise so minimalistic and easy to use would have a package that's so prescriptive - dropping all of the following files in the project root:
and then making the build dependent on the transform, while requiring |
I agree with you. My intention at the time was to improve the developer experience, but it looks like it backfired. In hindsight I should have packaged the t4 stuff separately. If you have a PR I would be interested to see what you have in mind. |
Is this fixed? - I'm still seeing this error with VS2017. |
I confess I did not look at this in ages and I agree with @discord that the
library could be simplified. Unfortunately I have zero bandwidth for this
at the moment...
…On Thu 16 Jul 2020 at 20:47, Adrian Sims ***@***.***> wrote:
Is this fixed? - I'm still seeing this error with VS2017.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHUAMDMDTBNKGKWD5GD6VLR35KM3ANCNFSM4CGT6FKA>
.
|
Hi,
While pulling from NuGet I get the following exceptionj. Same occurrs if I run the T3DocoptNet.tt T4 template.
The text was updated successfully, but these errors were encountered: