Can I use sql express to run WSS on windows server 2008 and if I can would this be a wise move?
Have a read of this article. You can use Windows Internal Database that's built into Windows 2008 as your database server.
The primary limitation is that SharePoint's application, web front end, and database roles all have to be installed on a single server. As usage of SharePoint increases, this could become a performance bottleneck. It's also not easy to move to a farm deployment - you would have to use SharePoint backup, reinstall SharePoint in a farm role, then restore your SharePoint data.
On the other hand, it's very quick to get up and running. There are also no database size limitations (a previously common misconception). You can use SQL Server Management Studio Express to manage the databases.
I can't give you a definitive answer, but here's something that happened to me once. I once installed Team Foundation Server on a Virtual Machine, and forgot to install SQL Server first. I expected the install to fail, but let it go, just in case.
It turns out that it installed SQL Server Express, and seemed reasonably happy with the decision. I don't think it got Reporting Services and such, but it seemed happy enough.
Go over to technet.microsoft.com and find the system requirements and install documentation for WSS. See if this is a valid configuration and what the issues might be.
Related
I have a problem, because I created NODEJS API and I have to deploy it on Microsoft IIS. I have never done this before. Is it possible to do? If yes, I will be very grateful if someone describes how to do this.
If you want to host node.js application, you should firstly install the node.exe and the a build of iisnode.
https://nodejs.org/en/#download
https://github.com/tjanczuk/iisnode
After installed the IIS nodes, you could set up samples, from the administrative command prompt call %programfiles%\iisnode\setupsamples.bat.
More details, you could refer to below article:
https://www.hanselman.com/blog/InstallingAndRunningNodejsApplicationsWithinIISOnWindowsAreYouMad.aspx
I don't think if that will help you but usually NodeJS don't need a server to be live unlike php or .NET so you can create a server on NodeJS itself and launched very easy .
also IIS used for statics content and .NET websites about 90% .
I'm developping a nodejs web application and I want to know how to deploy the app on enterprise level not on the cloud (Heroku and similar).
Please keep the explanation as simple as possible as I'm not an expert. I think that the answer to this problem should include something about having a local enterprise network but I don't know the details.
The end result should be that any user inside the enterprise could for example open the browser at some specific link and use the application.
You literally just need a computer connected to the enterprise network and your application running there.
For work, I need a free web server system to host a few web apps that I will develop. The server will be installed on Windows. The apps will need to be able to access a bunch of files on the intranet, and massage them. Mostly 10 people at same time will be using the apps. I would prefer to write code in .NET as it contains many great APIs, but I am not sure if the latest IIS Express has any major restrictions (number of clients connected to web server or database, etc.).
The other web servers I looked at (which are not .NET) are:
glassfish - seems that many are switching from it since Oracle stopped supporting it
wamp servers - there are many, the other day I installed wampserver and wrote an app in PHP to see how good it is. I must say PHP was very slow accessing my intranet files and processing them.
oracle weblogic server - never used it and have no idea how good it is
tomee - seems to be new and I do not know how good it is for web application development
I am wondering what do you recommend?
Thank you
first of all I very invested in TomEE. That here here is my feedback:
weblo, TomEE and GlassFish are java servers where wamp is a php/httpd one. Depending what you target it can be enough to make a choice (investment for java is more important than php).
If you choose java then weblogic is not free AFAIK.
Then TomEE is very close to TomEE giving you just all the power you need for web development so it is a safe choice (you'll benefit from a lot of integration and tools for free).
GlassFish is not bad by itself and the best way to select one server is to test it with a small app in your environment IMO.
I've just joined the Orchard CMS movement, but I'm having some major meltdowns about the setup. Their site has too much documentation about what I'm not looking for and it's making it tough to figure this out.
I plan to run about 15 brand new websites on one web/sql server and I have a separate development machine. I plan to make some custom themes and modules to suite each website's common and specific needs. I want to use IIS 7 and MS-SQL 2008 on the production server.
So, should I:
Just create the Orchard sites on the production server itself (With Web Platform Installer) and port in any themes and modules as necessary?
Or create the sites on the dev machine and Publish to the production environment with WebMatrix and WebDeploy?
I hate to create hello world sites on the production server and add content, themes, modules, etc as I develop them as in option 1. Or, in option 2 doing the web deploy introduces some complications such as database schema deficiencies because the site's db was created on the dev machine's SQL server and WebMatrix doesn't handle porting in the db schema during the Web Deploy (does it?). It seems option 2 makes it a lot more complicated.
What are other people doing in this situation?
Definitely the second option. WebMatrix should handle DB deployment just fine. You might want to take any problems you've faced with this to the WebMatrix support or forums.
I routinely deploy sites from my dev box to production, fwiw.
In a normal ASP.NET Website there is a Web Deployment Project that we can use to pre-compile our entire website and then we can safely upload this project to our production server in order to protect our code.
What can we do for ASP.NET MVC 2?
Link to it as is available today (RTM version)
Visual Studio® 2010 Web Deployment Projects - RTW
Make sure you install the latest security patches for your operating system and hire a good network administrator. No kidding. No matter what you do if a hacker gains control over the server he will get the code under one form or another even if it is precompiled. This being said it is a good idea to precompile the application and deploy only the assemblies instead of the source code. You could also consider obfuscating it also but this is something usually done for client applications which you deploy to your users computers and less frequently done in server side applications because you control the server.