Shulou(Shulou.com)06/02 Report--

It is believed that many inexperienced people have no idea about how to carry out the functional analysis of .net Framework 3.5. therefore, this paper summarizes the causes and solutions of the problem. I hope you can solve this problem through this article.

Microsoft requires technicians to maintain multiple versions of Visual Studio or load all projects into the current version of .net Framework. Targeting multiple is a welcome step forward, and .net Framework 3.5 can be found in both standard and higher versions.

Many technicians hope that Microsoft will make more progress in this area. Unfortunately, Microsoft does not provide a version targeting .net Framework 1.1, nor does it provide a simple two-way conversion between VS2008, VS05 and Visual Studio .net 2003 projects. This makes us feel a little disappointed.

.net Framework 3.5 has several new category libraries and language features, including language-level integrated queries, improvements associated with Web 2.0 and SOA, integrated workflows, peer-to-peer protocols, and Microsoft Office support.

All of these tools can be found in VS2008. For example, in Visual Basic.Net and Visual C #, language-level integrated query (LINQ) support is available in the standard version of VS2008 and later, including object-oriented design (Object Relational Designer), the SQLMetal command-line argument tools, LINQ-aware code compilers, and debugger support.

.net Framework 3.5 is a general mechanism with many possible components. .net Framework 3.5 introduces data queries into C # and Visual Basic languages to create syntax for queries that target in-memory data structures just as they are for file systems, XML files, and SQL databases.

There are several LINQ components and providers in VS2008, including LINQ for LINQ,XML for Objects (string, reflection and file directories) and LINQ for ADO.Net. ADO.Net 's LINQ consists of two components: DataSet's LINQ and SQL's LINQ. The more advanced ADO.Net entity framework and entity LINQ are not included in VS2008, but will be added as an auxiliary tool this year.

I tested SQL. Net Framework 3. 5 in C # for the SQL server 2000 database.

When writing the. Net Framework 3.5 query, Object Relational Designer created the C# type from the database schema smoothly, and the IntelliSense worked fine. On the other hand, the handwritten LINQ query for three related tables leads to some technical limitations in LINQ, and we all expect to get a LINQ that is comparable to the SQL Query Designer of VS2008 images.

After reading the above, have you mastered the method of functional analysis of .net Framework 3.5? If you want to learn more skills or want to know more about it, you are welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.