Geek Answers Handbook

Can anything make life easier for a dotnet 3.5 encoder captured in 1.1 world?

I have to spend a fair portion of my time developing in dotnet 1.1, and Iā€™m sure someone in a similar position will appreciate the more I use dotnet 2.0 and higher, the more annoying it is to go back to the earlier version. I'm getting more and more tired of messing with ArrayLists and the like when I want to work with Generics and ideally do it with Linq.

Can anyone recommend any tools, methods, libraries or anything else to make dotnet 1.1's life easier, especially given the disadvantages of handling fees mentioned above?

+6
generics linq
source share
3 answers

Tools: only one supporting Linux support for .NET 1.1 at http://support.microsoft.com/lifecycle/?p1=1249

Which shows that .NET 1.1 is already included in extended support (i.e. limited).

+3
source share

I recently joined a company that encoded in 1.1. I decided to take the application and transfer it to .Net 3.5 in due time and present it to the group. As a result, we are just going to release version 3.5, which opens perfectly in VS2008. This is probably not what you are looking for, but how I came across the same problem.

+3
source share

Hmm, it updates the .NET 1.1 application that you must support .NET2.0, not an option?

In 2004, I started developing a .NET application. This was in .NET 1.1.

Last year, we decided to "convert" this application to .NET2.0 using VS.NET 2008, and we did not encounter any serious problems.

All existing codes still work, and when new developments are to be made in the project, we can take full advantage of .NET2.0 (and, since we work in VS.NET 2008, we can also use the advantages of C # 3.0 (automatic properties lambda ...).

I always work with "Set warnings as errors", and for this project I have to disable this function, because some parts of the .NET 1.1 infrastructure are marked as "Deprecated". Although these classes still work, the compiler generates a warning that class X is deprecated, and you should use class Y instead.
But this is not a big problem, as you can gradually respond to these messages and adapt your code.

+1
source share

More articles:


All Articles