SubSonic, and Microsoft stopping support for LINQ - linq

I am a front end developer working on a small social network. Currently, we are using SubSonic and it has satisfied all of our needs. Since Microsft has stopped supporting LINQ, I want to know how this will affect the development of SubSonic if at all. Is there any reason to move to ADO.net?

Microsoft has not stopped supporting LINQ. I think you might be referring to LINQ to SQL, which is a completely different animal. If you're developing with SubSonic, you should have no issue with LINQ to SQL support.

LINQ is in no way going to stop being supported.
If you're referring to LINQ to SQL, you'd also be mis-informed. LINQ to SQL is indeed evident in .NET 4.0 / Visual Studio 2010.

I would also like to add: Linq and Linq-to-sql and two VERY different things.
I find it so frustrating that so many people don't understand this

Related

Moving a VB6 Application from SQL Server 2000 to SQL Server 2014

Interested to know if anyone has had any experience with moving a VB6 application from SQL Server 2000 to a newer version of SQL Server.
There are VB6 legacy apps on a Windows 2000 Server
These VB6 apps connect to a SQL 2000 Database
We are looking to upgrade from SQL 2000 to SQL 2014
We are reporting with Crystal Reports
The VB6 apps have inline SQL within them
I'd like to understand what the possible implications could be?
Thanks
For one thing, there is no direct migration path from 2000 to 2014. This article (http://sqlmag.com/sql-server-2014/sql-select-steps-migrate-sql-server-2000-sql-server-2014) outlines some potential steps to take to perform the upgrade.
Things that may trip you up not mentioned in this article:
DTS no longer exists so if you have any DTS packages, it will be a project to upgrade/convert them all over to SQL Server Integration Serices (SSIS) packages.
If your VB6 app contains hard coded SQL statements, rather than just calling stored procedures, you could have minor syntax issues that would have to be rectified (so test EVERYTHING)
If you are also looking to migrate VB6 to .NET, there is an upgrade wizard out there somewhere, but it is HORRIBLE, so depending on the need, it may be faster to just re-write from scratch. If you are implying that the VB6 application would just connect to the migrated 2014 database, the note on the main question is accurate, but again...test EVERYTHING.
3a. If you are referencing any old COM components or old OCX controls, it will be a source of pain.
3b. Does your app do any reporting? old 2000 SSRS, or Crystal reports? again, another project.
Good luck!
I've done it, and there were stored procedures / user functions that needed to be updated for compatibility. Here is a Microsoft tool, SQL Server Upgrade Advisor. If you are using inline SQL in your code I'm not sure if this tool will help you. I was fortunate in that most on teh application SQL was implemented as stored procedures inside the database itself.
Here is an MSDN blog post about upgrade considerations and using the Upgrade Advisor tool.

NHibernate 3.3 or Entity Framework 4.3 for Oracle 11g and ASP.NET MVC 3.0?

I have to choose between last versions of NHibernate (3.3) and Entity Framework (4.3) to work with Oracle 11g; a very special issue with our architecture is: we have to execute a lot of stored procedures to keep balance with others old systems.
We're gonna use ASP.NET MVC 3 for user interface. so, can you help to choose which is more convenient for our architecture between NHibernate and Entity Framework?
I have read that Oracle driver for Entity Framework is very new, so, I can't decide yet.
MS is very committed to EF but they are not developing provider for Oracle! Is Oracle committed to EF as well?
The best way to make decision is to create a short POC (proof of concept) where you evaluate both tools on some easy and intermediate problems (you can also try a hard problem) you will have to solve in the real project. This will help you understand challenges in both tools on your real problems not only in some imaginary discussion. It will also help you understand difficulties in adopting a new technology and integrating it with your existing environment.

How to use VS and EF to access databases like Oracle and others?

What options do I have to connect from VS 2010 to other databases like Oracle etc.? What's the best solution?
Now I'm using entity framework (for MSSql DB) and would like to know if it's posssible to use it also for Oracle? I think there are some third party solutions but want to avoid them because of the costs.
Thanks in advance.
Regards.
There is this possibility
http://linqtooracle.codeplex.com/
then there is nhibernate
And also this other one
http://www.oracle.com/technetwork/topics/dotnet/index-085163.html
You could just install the Oracle Data Access Components (ODAC) that automatically integrate with Visual Studio. Other databases would likely have something similar.

Comparison of 3rd Party Oracle .NET Providers

I'm in the process of cleaning up an Oracle database application. In this application, performance and ease of access are paramount concerns. It has to get out of your way and let you get to the data in a free and uninhibited way. While doing that, it has to be very fast. When it can't be fast, it has to be multi-threaded so that it doesn't freeze up the system.
All of that out of the way, here's what I've learned. Microsoft has deprecated the System.Data.OracleClient namespace. It'll be around in .NET 4.0, but it'll be marked with ObsoleteAttribute. I've currently swapped it out for ODP.NET from Oracle (which turned out to be surprisingly painless), but in reviewing other comments, I realized that I was still failing to meet a few design goals:
I might not be using the fastest provider out there.
I still can't seem to provide access to the SYSOPER account. I haven't quite worked out why, yet. That could be a coding issue, but I'm stumped.
So here's my question for you guys.
What are the 3rd party alternatives to System.Data.OracleClient that you've used, and what are their pros and cons?
I used ODP.NET and I'm satisfied with it.
There were some cons, which are gone with the last version of oracle instant client supporting odp.net.
We've used ODP.NET since it was first released and have been pretty happy with it. I haven't used the following, but the fact that you can use them without installing an oracle client is appealing:
DevArt
DataDirect

LINQPad and Oracle

Does LINQPad work with Oracle? Has anyone tried? What do you suggest?
As of beta version 4.35, LINQPad supports Oracle fully - you can now do "LINQ to Oracle" queries. I believe it uses the DevArt dotConnect libraries for managing this great feat. Further, in addition to native OCI support, it also supports a direct mode which does not require the Oracle OCI DLLs to be present.
To enable this feature you will need to simply add a new data connection in LINQPad, and when asked which driver to use - click the View more drivers... button. You can then install the IQ Driver and use it for querying Oracle, MySQL and SQLite databases.
Judging by their user voice item request for Oracle support, it appears unsupported at the moment.
A comment on the O'Reilly forums also suggests its not supported.
update As we understand it, there's now built-in Oracle support in the latest versions of LinqPad; the home page of LinqPad now lists support for Oracle.
update January 2013 The new LinqPad-to-Oracle support appears to still be available. Per the LinqPad FAQ:
Q. Why does LINQPad use LINQ to SQL under the covers, rather than Entity Framework?
A. LINQ to SQL is faster with large schemas and in most cases, emits
better SQL. You can, however, use EF with EDMs that you define
yourself. For querying SQLite, MySQL and Oracle (via the optional
plug-in), LINQPad uses Matt Warren's IQueryable toolkit.
Linqpad now has support for lightspeed which supports oracle.

Resources