I am developing a SAAS application using MVC 3 and Windows Azure. I am developing in Visual Studio 2010.
As I will have a main website which promotes the product, what I want to be able to do is have my website and application separate. Would this be feasible to do it in the same solution and add as a separate project?
sure in Visual Studio 2010 you can have different projects in the same solution.
You can for example create a class library project for the Business Logic, another one for the Entities, a common one for the interfaces and another one for the data layer (with or without Entity Framework models...).
In the same solution you can then add a web application project which uses MVC 3 and C#.
In general for big projects you would have multiple solutions with many projects inside any of them. It depends really on the size of your whole architecture.
To decouple things nicely, you should imagine to communicate from MVC site to the business logic not via direct project reference but for example via web servives (XML or better WCF), so your business logic can be installed aferwards also on another machine than the web servers (for example an application server) and the web ui will just use a different machine name or ip address to direct all the WCF calls. we use this approach successfully in several projects.
Related
I'm using Visual studio 2015 to develop multiple angular2 single page apps. The applications share some common components (Login, header, footer etc) and also I like to have only single node_modules accessible to all the apps. The apps are in single VS project within their own directories current setup that I have:
As per the best practices what is best structure for the VS solution/project?
Maybe you should consider creating ONE app but with MULTIPLE ng2 modules like DealFinderModule, JobBoardModule, SharedModule. Using modular system is considered to be the best practice and will help you achieve your goals
I have a lot to do with nodes and edges. I need to pull from a file/store, draw the graph, and allow interaction to apply filters or rendering styles. Graph Dracula seems perfect.
Unfortunately, I have only the basic understanding of HTML, JavaScript. I feel like AngularJS or the MVC pattern in general is what I need, but it's hard for me to get started. I'm having to learn too much all at once.
Can anybody refer me to a platform or recommend a basic set of html views & scripts that I could use as a launching pad for the MVC part?
At my company we are using ASP.Net MVC to build web applications. Such applications are meant to be hosted inside an Microsoft Internet Information Services server or in the Azure cloud.
If you start in Visual Studio 2015 with File > New ... > Project and then select Templates -> Visual C# -> ASP.Net Web Application -> MVC , Visual Studio will scaffold a project that already works in principle and where you can add your content.
See http://www.asp.net/mvc for tutorials etc.
For data persistence, Microsoft Entity Framework works well with the MVC stack, see https://msdn.microsoft.com/en-us/data/ef.aspx for more.
Is there a known way to configure JuiceUI to exist in one Visual Studio Web Application project and reference it from another Web application? We want a centralized location for all of our Web Application to use it instead of having to install the JUiceUI.dll and Scripts folder in every project.
Thanks
I'm not sure if Visual Studio 2010 already does this or not with respect to how it packages Azure deployments, but I have a Visual Studio solution which contains 5 projects:
The Azure Service Project
The project for my web role
2 class library projects which
contain the DAL and BLL that my
roles use
And one MS Test project used for
unit and integration testing across
all of these projects
My deployment package right now is roughly 100 mbs, and takes a while to upload. I have some other things I can do to make it smaller, but what I want to know is if there's a way I can make sure that the MS Test project isn't being packaged alongside everything else given that it has the largest footprint. Any suggestions, or is this not actually a problem?
As long as there are no references from your web role, the DAL or BAL projects to the test project, then it shouldn't be included in the package.
If you're worried about it I would first of all double check all of the references in the web role, DAL and BLL projects to make sure that you're not accidentally referencing the test project.
As long as that is OK, I'd then do a publish of the project to disk and then have a poke around in the \bin directory if the cloud project to see what's actually using up all of that space.
Just as stated before is you do not have any references to your test project in your web role you should not worry for having it deployed alongside the rest of your code.
Another thing I would recommed is to just precompile your web site and
add it as another site in your file using a host header for it.
The advantage of that is that you can create a msbuild task to precompiled your site and just upload it.
Also I reposted about a solution for putting your view files in azure storage which will allow you to modify appearance without going thru the republish process.
http://blogs.artinsoft.net/mrojas/archive/2011/05/01/windows-azure-and-websites-in-a-flux.aspx
Almost all of our Windows projects consist of a WCF windows hosted service and then a WPF client application. All of these have usually been split into two different solutions, one for the service, one for the client. This was done for various reasons, but we recently were looking at possibly putting them all together on a new project, which we did. This would mean not having to run two copies of Visual Studio and make it easier for various other things.
Our concern now is being able to edit the WPF client while debuging the service. Many of the developers will keep the service running a large part of the day when making changes in the client. But it looks like with this setup, when you start debuging the service, Visual Studio will not let you edit any of the other code in the solution.
Is there a way around this, so that you could have the service running whenever you want, and still be able to edit the WPF and CS files in the other project? Or should these two parts stay in two separate solutions?
You'll want two instances of Visual Studio: one doing the debugging of the service and the other one for coding.
You could also imagine having the service running without the debugger attached, and only attach it manually when you're ready to launch/debug the client you were working on.