My situation is that I developed a .NET 4 based MVC2 web app, and now I have to deploy it on a Windows Server 2003 that has standalone SharePoint 2007 living on it. My quick research shows that SharePoint 2007 doesn't play with .NET 4. So my questions are:
1) Will SharePoint 2007 break if I install .NET 4 on the server? As far as I know .NET versions were backwards compatible...
2) Is it possible to deploy the .NET 4 assemblies with my web app without actually installing the framework and registering it.
3) Any other tips and advises on resolving this situation?
SharePoint wont'break if you apply latest service packs + cumulative updates to it.
At least I have such a combination running on my servers right now.
It would be a problem, if you tried installing .Net4.0 on the same machine prior to "Infrastructure update" of 2009 (or maybe before SP2?), since, as it was said "SharePoint stored some references to .net4 classes in the configuration database", whatever that means.
Related
We have an ASP.Net website running under the 4.0 framework in IIS 7.5 on a Windows Server 2008 R2 box. A portion of the web site functionality utilizes WCF and has a "standardEndpoints" section in the web.config.
The website works fine and everything works fine if we want to use the IIS Management Console GUI to do things.
We would like to use powershell to make changes to the web.site but when we run "Set-WebConfigurationProperty" an error is generated indicating that the "standardEndpoints" section of the web.config can't be processed.
The hotfix referenced here is not the solution. The website works, the hotfix appears to be only for Server 2008 (not R2), and when you try to install it, it says "not applicable for this server".
We did discover by running $PSVersionTable that PowerShell was referencing version 2.0 of the CLR. We installed Powershell 3.0 and now Powershell is referencing version 4.0 of the CLR but the problem persists.
We are looking to see if there is a simple solution to this. I suspect we may not have the right version of the IIS management script dll but can't find a different one to use. If the solution gets to complicated, we will just wipe the server and start from scratch.
Thanks for any suggestions,
John
I will need a Sharepoint Server 2010 install for learning purposes.. I already have a Win 7 x64 os installation with vs2010 and I use it for my current development needs.
The question is ... would you recommend to install sharepoint onto an existing win 7 installation, create a separate OS instance (win7 or win 2008 r2?) for sharepoint development purposes or maybe create a VM for that? I have 4GBs of ram and I wont be able to extend it.
What are your experiences with dev environments for sharepoint 2010? I remember that 2007 was a real resource hog - maybe there is a 'magical' switch that allows sharepoint 2010 related services to be turned off?
If you thought SharePoint 2007 is a resource hog, SharePoint 2010 is even worse. The full installation creates lots of Windows services and IIS application pools. Which makes it really hard to stop SharePoint since all those services start automatically.I agree with others that you should use the VM approach but I think you need Windows Server 2008 R2 to be able to create 64-bit VMs.
Here's a link to powershell scripts for stopping/starting SharePoint services: http://blogs.msdn.com/b/emberger/archive/2009/11/16/stop-and-go-with-sharepoint-2010-on-your-workstation.aspx
I personally always run it in a different instance - either a separate machine or a virtual machine. Sharepoint 2010 is massive, and changes your system with a magnitude not seen by any previous sharepoint version, in terms of databases, scheduled tasks, services...
You should install your SharePoint 2010 in Server2008 R2 if you can ,since then you can do a complete install and use domain account.The installation in win7 is a standalone install and only use system account.It does not match what is in production...
Or if you can, virtualize your SharePoint environment.You need to give at least 4gb ram to SharePoint VM otherwise it is running like a dog.
I'm relatively new at creating custom content for Sharepoint 2010 and have been having some difficulty understanding how to get non-design related components (ie. web parts, custom classes, ...) into a Sharepoint site. I have created a new visual web part on the company's development server and deployed it successfully from Visual Studio 2010 and also packaged the solution into a WSP file.
What is the best way to go about getting that web part onto the production server? There is currently no Visual Studio install on the production server but from searching around I get the feeling that it might be possible to do this remotely using Powershell or STSADM. Has anyone faced a similar situation?
Use PowerShell. Stsadm is considered to be obsolete and is included in SharePoint 2010 only for backwards compatibility with SharePoint 2007. So, since you are new to SharePoint, pretend Stsadm doesn't even exist.
My PowerShell scripts keep evolving, but they are based on samples from Ted Pattison:
Chapter 2: SharePoint Foundation Development (scroll down to Using Windows PowerShell Scripts to Automate Tasks in Visual Studio)
PowerShell Boot Camp for SharePoint Professionals
I am currently in the early stages of developing a couple web applications, I have not written any code yet as I am still just gathering requirements and scoping things out. I want to target ASP.Net 4.0 winforms as the platform for these apps but I want to make sure there are no glaring issues with this new version before I commit.
I understand that if I was porting an existing app from 2.0, 3.5 to 4.0 there may be issues but I am starting from scratch on these projects and plan to write these apps to support the new features of 4.0.
Should I wait for the first service pack to come out? Just seems like more work to start with 3.5 now only to go back through and tweak things for 4.0 in just a few months or even before I finish the app.
Our servers are Win 2K3 with IIS6 and MS SQL 2000, Should I expect any problems with VS 2010 and MS SQL 2000 in regards to Linq to SQL and EF?
Do it. I do the same at the moment. SQL 2000, though - is out of support. Even the bank I am sitting in at the moment is now replacing it with 2005 / 2008. I would seriously consider upgrades.
Web application? Using SPLA (only legal licensing for service providers - purchased licenses are not legal here) you get 2008R2 and SQL 2008 R2 anyway.
well, according to what I've found googling around, it's imposible... (maybe with with windows xp 64...)
but I thought that maybe someone could find a way to achieve it, or at least some workaround...
http://www.iisanswers.com/IISFAQ.htm
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.inetserver.iis&tid=14654991-875f-4cc6-a853-7e9f3bb96bc3&cat=en&lang=en&cr=&sloc=en-us&m=1&p=1
--
ps: I need to debug classic asp code, and my production environment is windows 2003, while my development machine is windows xp...
--
edit:
just to clarify, I can already debug classic asp code in iis 5 with vs 2003 and 2008, it's just that I stumbled upon a (very silly) bug that only appeared on iis 6 (when IIS 5 received and empty http status, it just assumed 200, while iis 6 kept asking for my credentials in an infinite loop, it was very silly in deed, but took me a lot of time -and cursing- to discover it)
IIS 6 cannot be installed on Win XP. However, debugging classic ASP code is possible on Windows XP / IIS 5.1 using Visual Studio 2003 and up. You will need to configure IIS 5.1 to "enable ASP server-side debugging" (disabled by default):
IIS settings http://www.freeimagehosting.net/uploads/f1a6f781b9.png
Here is a more detailed article on how to debug classic ASP pages in Visual Studio - link
(NOTE: When running on XP Pro/IIS 5, you need to attach to dllhost.exe instead of w3wp.exe)
You posting in your 2nd link is correct. And read the faq. That spells out why it can't be done.
One option you can do is have a virtual machine of Server 2003 running on your laptop.