Administrator
VB.NET Forum Admin
- Joined
- Jun 3, 2004
- Messages
- 1,462
- Programming Experience
- 10+
Dear Component Vendors:
I ask "why are you still supporting VS.NET 2002/.NET Framework 1.0"? As most are using VS.NET 2003, we are being penalized by your components being compiled against an older framework. It's as if everyone is using Windows XP but you're still supporting Windows 98. When Whidbey arrives (VS.NET 2005) are you still going to ship components compiled against .NET FW 1.0?
I see some vendors shipping two assemblies, one for .NET 1.0 and the other for 1.1. My suggestion, stop promoting older OS's and frameworks and help push the developer community to the most common/latest framework. When Whidbey ships, I certainly expect to use the latest and greatest components/versions...so please, stop supporting the obsolete and promote modern computing!
Thank you!
I ask "why are you still supporting VS.NET 2002/.NET Framework 1.0"? As most are using VS.NET 2003, we are being penalized by your components being compiled against an older framework. It's as if everyone is using Windows XP but you're still supporting Windows 98. When Whidbey arrives (VS.NET 2005) are you still going to ship components compiled against .NET FW 1.0?
I see some vendors shipping two assemblies, one for .NET 1.0 and the other for 1.1. My suggestion, stop promoting older OS's and frameworks and help push the developer community to the most common/latest framework. When Whidbey ships, I certainly expect to use the latest and greatest components/versions...so please, stop supporting the obsolete and promote modern computing!
Thank you!