-
I've recently had the pleasure of working with some SSIS packages, and I can't say I've been too impressed with the development and debugging experience. I think my advice here would be to give some serious thought to what it's going to be like to support a solution like this, including (very important) *who* is going to be doing that
-
I did this with a prior version of CSLA, and I now have another case where I'd like to be able to do something like this. I understand that inheritance of base business objects adds some complexity, and I know it's a tricky case to model into the framework, but I think it's important to acknowledge that there are cases where there's
-
It probably depends on how you're implementing the rest of your app. I have a feeling that you'll receive better answers if you can share just a bit more context with your question.
-
As others have commented, CSLA's survived a number of "game-changing" technology onslaughts already. I think the key is in looking at what happens to apps as they grow up. There are a number of tools that'll get you out of the gates quickly, but as you start to add on all the stuff needed to make an app "real", you start
-
Is a web client a possibility? This might let you run .Net 4.0 on the web server, at least.
-
Wouldn't you really want your LOB application to be just another module? You can certainly write them separately and then integrate, but if you're going that route, why not just start with DNN or another CMS starter kit and save the trouble of building that part of the app?
-
Go to the topic list for the forum and look near the bottom of the screen where it lists "Page 1 of ..." -- there's an RSS link at the end of that text. The link for the code-gen forum, btw (note the ForumID, which is different for each forum): http://forums.lhotka.net/forums/rss.aspx?ForumID=9&Mode=0 Many browsers will also show the
-
If I understand correctly, you're trying to combine the output of both projects into a single assembly (dll) - if I'm reading this right, I believe that could be the problem. You can have two projects share a namespace, but each is going to have to have its own assembly name, and when you build your Web project, you should see both dll's
-
Sorry - I read right over the part about it being a project reference. You probably already verified that the assembly is being written into the bin folder, right?
-
I just ran into this myself w/ an MVC project. Check the <assemblies> section of your web.config to see if the reference is present there. If not, try adding it.