I am going to create a basic CRUD application that will live inside Sharepoint 2010. The data will be hosted on a SQL 2008 R2 server.
Basically, there will be several “Add” forms, some queries and some reports (SSRS).
Honestly, the application doesn’t really need a Sharepoint, but we are trying to get as many applications as possible hosted inside Sharepoint. (The application is currently a Microsoft Access application.)
I have experience creating these types of applications (ASP.Net) and have recently used the Entity Framework. Typically, I create my data layer in a separate Visual Studio project (using EF), and then extend the partial classes that it creates, and / or sometimes create a different POCO level to access the data (depending on how "business" -logic "exists).
Anyway, I have a question:
If I create a solution (Visual Studio) (I know that I need to target .Net 3.5, because SP does not yet support 4.0), can I use my usual “multi-level” design and create a separate project (assembly) that coordinates all my access to data (Entity Framework), and then has a separate project containing all the components of Visual Web (which we are developing in the form of data entry)? Will this work? Can I call exposed methods from (EF) DAL from Visual Web Parts (after deploying my solution to the SP server)? Do I have to do something “special” or will both projects be packaged into a file (what is it) “wsp” and deployed to SP? (Or I will have to manually add my DAL assembly to the GAC, etc.)
Any examples or tutorials would be a big help for me.
, , , , . ? ( , BDC SQL Sharepoint, . - , " " ... , "" ASP.Net, SharePoint "-".)
!