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.
Related
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.
I know that SharePoint 2010 uses .net 3.5 and since .net 2 (3.5 with sp1) has different CLR than .net 4, what is the best practice to use Entity Framework 4 (4.2) with it?
Is the web service (WCF service) the only solution for it?
If not, what is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Is the web service (WCF service) the only solution for it?
Yes. You have to do cross process call because your main process is .NET 3.5 and you need another process running .NET 4.0.
What is the best ORM similar to EF from simplicity and productivity prospective is recommended to use to connect to MS SQL Server? (may support oracle later)?
Other alternatives are for example NHibernate or LLBGen Pro. Both are supported in .NET 3.5. You can also try Linq-To-Sql or SubSonic.
What is the latest version of SQL Server CE? And what is the download link? I Googled and the link I got there is not working. I would prefer a stand alone installation and not part of Webmatrix. Is this possible?
I would like to use it for my testing in ASP.NET MVC 3.
I know this is not a programming question :)
Abe has linked to SQL Server CE 3.5 which is probably your best stable choice. However 4 is now out (ScottGu blog) and you can download it from here
Microsoft SQL Server Compact 4.0
or through WebMatrix - although the VS2010 tooling is in the service pack which is still in beta.
I'm building a .NET CF 3.5 application that will communicate with an server based MS SQL server 2005.
The communication will happen trough the devices's WiFi connection.
I've been looking for a good O/R mapper and am a bit lost. Most sites/people assume that you're going to work with a local compact database and not with an external "normal" SQL server.
In the past, I've worked with entityspaces (but that seems to be commercial now?) and lately with linq-to-sql.
What good easy to learn & implement O/R mappers run on a .NET CF app with normal MS SQL database?
I did this a few years ago with .NET 1.1 and LLBLGen with great success.
I have a reporting services project with lots of reports developed in SQL server business intelligence development studio that comes with sql server 2008. I want to deploy these reports to a server that has reporting services 2005 only but the deployment is failing. I'm wondering if any one around here has been able to deploy reports developed in business intelligence development studio 2008 to a server running reporting services 2005 only.
If it isn't passible, is there a way of downgrading my report project back to reporting services 2005 so i can be able to deploy my reports?.
Unfortunately this is not currently possible.
The following thread contains a discussion from the MSDN forums pertaining to a similar query. If you read through it, you will discover that an MVP raised this as a development/support request with Mcrosoft.
http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/686cac48-bc14-4978-b7bf-acbc0c90384e/
Is it really that bad?
For going from 2005 -> 2000, you just had to strip a couple of lines of xml out of the rdl file.
Can't you do something similar? Assuming you don't use 08 specific things like Tablix
?
Microsoft, you don't know how huge of a pain in the butt this problem is. And we're left to find out about this incompatibility only after creating reports in VS 2008 and trying to run them on SQL Server 2005.
This is extremely poor product management on Microsoft's part.