|
-
Mar 18th, 2009, 08:36 PM
#1
Thread Starter
Frenzied Member
Version Tag
Just wondering how the version tag at the beginning of the thread title would look if it was half the size.
VB 2005 Thread Title
Just seems to distract from seeing the title clearly.
By the way, thanks for letting me be apart of this excellent service.
-
Mar 18th, 2009, 08:50 PM
#2
Re: Version Tag
Good idea, also I think the "vs" part should be taken off since we already know that the topics are in the "VB.net" forum.
-
Mar 19th, 2009, 12:06 AM
#3
Re: Version Tag
Well IMO I think keeping thread Prefixes (tags) short as possible is better. Like we previously had just the year versions as the "VS " part is redundant
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
Mar 19th, 2009, 04:21 PM
#4
Re: Version Tag
I'd honestly consider using .NET versions as opposed to VS. VS2008 and beyond support framework targetting, so just because I'm using VS2008, I may not be using 3.0 or 3.5. VS2008 is a much faster and expandable IDE than 2005 was, and IMO, everybody should be using it.. but it's ultimately the version of .NET that matters, not the version of VS.
-
Mar 19th, 2009, 04:35 PM
#5
Re: Version Tag
 Originally Posted by timeshifter
I'd honestly consider using .NET versions as opposed to VS. VS2008 and beyond support framework targetting, so just because I'm using VS2008, I may not be using 3.0 or 3.5. VS2008 is a much faster and expandable IDE than 2005 was, and IMO, everybody should be using it.. but it's ultimately the version of .NET that matters, not the version of VS.
I dont say this very often ( ), but I actually agree with TS on this one..the main difference lies in the .NET version. Thats the way its set up in the C# forum.
-
Mar 19th, 2009, 04:54 PM
#6
Re: Version Tag
Yes we initially discussed this and I believe the decision was because 3.0 or 2008 were not released yet so going with 2005 didnt create the issue that 3.0/2008 did. Why we have it in C# and not vb.net :shrug:
Thread Prefixes "could" be changed but thats not my call, its Joes/Brads
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
-
Mar 19th, 2009, 05:26 PM
#7
Re: Version Tag
Understood. The point of my post wasn't to make a demand, merely to raise a point that the current prefixes don't do much to actually inform us of what technology we should be prepared to help with. Granted, for a lot of us, it probably isn't an issue... I'll work just as well with 2.0 or 3.5, although I much prefer having the LINQ extensions available, as I play with Generics a lot. Either way, version of VS just plain isn't helpful anymore, because of the framework targeting. This is just posted here so that somebody in charge can see it and think about it.
-
Mar 19th, 2009, 08:58 PM
#8
Re: Version Tag
Yes points agreed and hoping for the same and at minimum the removal of the "VS " part. Too long and FW vresion would make that even shorter
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum. 
Microsoft MVP 2006-2011
Office Development FAQ (C#, VB.NET, VB 6, VBA)
Senior Jedi Software Engineer MCP (VB 6 & .NET), BSEE, CET
If a post has helped you then Please Rate it! 
• Reps & Rating Posts • VS.NET on Vista • Multiple .NET Framework Versions • Office Primary Interop Assemblies • VB/Office Guru™ Word SpellChecker™.NET • VB/Office Guru™ Word SpellChecker™ VB6 • VB.NET Attributes Ex. • Outlook Global Address List • API Viewer utility • .NET API Viewer Utility •
System: Intel i7 6850K, Geforce GTX1060, Samsung M.2 1 TB & SATA 500 GB, 32 GBs DDR4 3300 Quad Channel RAM, 2 Viewsonic 24" LCDs, Windows 10, Office 2016, VS 2019, VB6 SP6 
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|