codesmithtools / Templates

CodeSmith Generator Templates
http://www.codesmithtools.com/product/generator
54 stars 35 forks source link

Csla4 #711

Closed jasona22 closed 6 years ago

jasona22 commented 6 years ago

Hope I am doing this right. I've never used this tool before. Dates make this feel really old and not current. Anyhow, doing a CSLA project and need latest CSLA templates. Using VS2015, current .net and SQL Server. Not sure what else I am supposed to put into this pull request.

jasona22 commented 6 years ago

NO! I don't want ot merge anything. I want to pull the latest templates. This github stuff stinks.

niemyjski commented 6 years ago

You'll just need to click the download button or clone button on the main page of GitHub. Please feel free to submit any updates to the templates.

niemyjski commented 6 years ago

Also, the latest templates are in master.

jasona22 commented 6 years ago

Yea, I was in Master. I didn't want every framework and project and when I drilled down the "Clone and Download" vanished. HOWEVER, I figured out not to drill down but use the drop down. That's clear! (not your fault; just annoyed at bad interfaces and I feel Git has bad interfaces).

My exasperation aside, I am clearly doing something else wrong. I pulled the CSLA project down and it will not compile. The odd thing about it is I have like 380 errors. But as I select each error to get an idea of what the problem is, the red squiggles vanish and the error count goes down. I can continue looking at each error in turn until the entire project says 0 errors. Then rebuild and have 380 again. Kind of makes me think of the 99 bugs in the code song. I don't really think there are bugs, but the behavior is rather odd. I don't see any NuGet packages. Any experience with this behavior? None of the references are complaining.

Thanks in advance.

J

niemyjski commented 6 years ago

I fixed the issue, you should now be able to pull latest and build. It was targeting .net 4.0 and I upgraded the references to .net 4.6.2

jasona22 commented 6 years ago

Thanks. So I was going to try to add the "entites.csp" to my library solution and add things one at a time but wasn't having success. Watched the "quick start" video and thought I would try that just as a "lets see" kind of thing.

However, upon completion, I get the following error:

"We were unable to automatically populate your Visual Studio Team Services accounts.

The following error was encountered: VS30063: You are not authorized to access https://app.vssps.visualstudio.com."

I don't really understand. I am not trying to do anything with team services. My other projects all load fine.

My normal, day job, I use the CSLA project. Over the past 7 years, we customized it very greatly. However, I am working on a side project and thought I'd try to use the CSLA framework right out of the box as it is written and so far, I've not been able to get a single try to compile. The entites.csp was the closest. The quickstart wont even load in VS2015.

Isn't it sad that I have a 7 year CSLA project that I can skate around with no problems, but I am stumped by the samples! GAH I feel dumb.

First would be curious how to get the QuickStart to work. I'd think the project it builds should be able to be loaded in VS2015.

On my entites.csp project attempt, I load an editable root object, a readonly child and readonly list. I load a command object for the ExistsCommand stuff and then get an ADOHelper error. Where exactly does that come from? Is the ADOHelper in a template or do I just need to build one? My day job we use a custom Data Access Layer (DAL) and Factories.

The plan for this project is to not customize anything from codesmith/csla. To build the library and let the UI developers add their wpf/xaml UI on the library. I need to keep it simple so once my contract time is done with them, they can carry forward without a lot of CSLA/Codesmith knowledge.

Thanks in advance.

On Tue, Aug 21, 2018 at 8:23 AM Blake Niemyjski notifications@github.com wrote:

I fixed the issue, you should now be able to pull latest and build. It was targeting .net 4.0 and I upgraded the references to .net 4.6.2

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/codesmithtools/Templates/pull/711#issuecomment-414671991, or mute the thread https://github.com/notifications/unsubscribe-auth/AnXOjsXzvNcEt6lw3fT6nSTimD8V2wJMks5uTAnTgaJpZM4WCxsO .

niemyjski commented 6 years ago

I don't think anything should be reaching out to team services. My only thought is when you try to generate in project that's tied to source control we call api's to try and check out those files. Yes, some work needs to be done for the new visual studios. In Generator 8 we broke it by moving to a generate on build based nuget package so the targets file is no longer there. AdoHelper is a template that gets rendered.