I am new to this project and eager to test the power I am hoping it will provide me. I have been able to finally get a build to compile. However, I had to do a few things manually to get everything happy. Below is the list. Please confirm if this is expected behavior, a known issue or something else that may be unique to me.
Observations:
1) Barking about Microsoft.CSharp.dll not being found (and a couple other related errors). Located some info about that being due to use of Lamda expressions, which I do. No problem, added the explicit reference to the DLL and all good.
2) As confirmed in another recent thread, base view type is not being set for the views, just the model set in <> and no type. I have tried using my custom base view, fully qualifying the view, and even using the built-in view. Nothing produces a complete base type reference in the class and I have to manually add the base type so it can compile.
3) Additionally, none of my added namespaces in the web.config are being added to the generated class, thus tons of reference issues. Seems like web.config in neither the Views folder nor root level is being used. Adding the namespaces explicitly to each view, allows it to compile.
4) While model is explicitly set in the view, any use of the generic HTML editor helpers end up with an object reference thus the Lamda expressions are failing. Tried a couple different things, but cleanest workaround was to fully qualify the model class, even though the namespace had been added to the view already. For example, this didn't work:
@using VideoLibrary.Application.Messages
@model VideoMessage
But this did:
@using VideoLibrary.Application.Messages
@model VideoLibrary.Application.Messages.VideoMessage
Comments: OK, thanks again for the quick reply. My bad. For some reason, when I looked at the older solution, it appeared to me to be 4.0. Clearly my mistake. I will take that one down again and start there. And I know you weren't saying there are no issues - I expect there to be issues - with anything. I was just wondering if any of my observations were ones anyone was already familiar with. With the namespaces, yes I had added them to both placements of web.config, to see if one or the other was the one being read, but no avail. Actually, part of the hesitation to spend too much time on these particular concerns was because I am still unsure if I will have issues when using the generated views, in the target project. Note that my intent is to have these as referenced libraries (aka discovered plugins). Because I have many other dependencies that have to be resolved based on the framework I have built, I am anticipating running into further issues and one or more might be a deal-killer. No reflection on your project and what it does - would be more on my end and my constraints. So...what makes sense now then is since I have this compiled (albeit with some massaging), to test it in the agnostic project and see if it will work in my target scenario. If it does - that would be awesome - then I will return to working out the generation nuances with your test solution and report back as required. Thanks again for your efforts! Mike
Observations:
1) Barking about Microsoft.CSharp.dll not being found (and a couple other related errors). Located some info about that being due to use of Lamda expressions, which I do. No problem, added the explicit reference to the DLL and all good.
2) As confirmed in another recent thread, base view type is not being set for the views, just the model set in <> and no type. I have tried using my custom base view, fully qualifying the view, and even using the built-in view. Nothing produces a complete base type reference in the class and I have to manually add the base type so it can compile.
3) Additionally, none of my added namespaces in the web.config are being added to the generated class, thus tons of reference issues. Seems like web.config in neither the Views folder nor root level is being used. Adding the namespaces explicitly to each view, allows it to compile.
4) While model is explicitly set in the view, any use of the generic HTML editor helpers end up with an object reference thus the Lamda expressions are failing. Tried a couple different things, but cleanest workaround was to fully qualify the model class, even though the namespace had been added to the view already. For example, this didn't work:
@using VideoLibrary.Application.Messages
@model VideoMessage
But this did:
@using VideoLibrary.Application.Messages
@model VideoLibrary.Application.Messages.VideoMessage
Comments: OK, thanks again for the quick reply. My bad. For some reason, when I looked at the older solution, it appeared to me to be 4.0. Clearly my mistake. I will take that one down again and start there. And I know you weren't saying there are no issues - I expect there to be issues - with anything. I was just wondering if any of my observations were ones anyone was already familiar with. With the namespaces, yes I had added them to both placements of web.config, to see if one or the other was the one being read, but no avail. Actually, part of the hesitation to spend too much time on these particular concerns was because I am still unsure if I will have issues when using the generated views, in the target project. Note that my intent is to have these as referenced libraries (aka discovered plugins). Because I have many other dependencies that have to be resolved based on the framework I have built, I am anticipating running into further issues and one or more might be a deal-killer. No reflection on your project and what it does - would be more on my end and my constraints. So...what makes sense now then is since I have this compiled (albeit with some massaging), to test it in the agnostic project and see if it will work in my target scenario. If it does - that would be awesome - then I will return to working out the generation nuances with your test solution and report back as required. Thanks again for your efforts! Mike