How do I convert these statements from Visual Basic 2008 to Visual Basic
in Visual Studio 2003?

Namespace IVSSEventHandlerxx

     <ProgId("SourceSafe.Changes")> _
     <Guid("eeeeeeee-ffff-1111-2222-cccccccccccc")> _
     <ComVisible(True)> _
     Public Class test

         Implements IVSSEventHandler, IVSSEvents

I am mainly concerned about the attributes.

Thanks,

Frank

The best way to start is to post your question to the correct newsgroup.
This is a Visual Basic group and the products that you are using are not
Visual Basic, despite their deliberately misleading marketing names. Visual
Basic code will not work in Visual Basic 2008 or in any other similarly and
dishonestly named dotnet product (confusing, isn't it, but then confusion is
exactly what the dishonest Micro$oft fairground gypsies were after). Try
posting your question to:

    microsoft.public.dotnet.languages.vb

Mike

Hi Frank,

There shouldn't be any problems with that, it may just be your references
and imports. As your post is to do with .NET, best to ask your question in a
dotnet forum such as :
microsoft.public.dotnet.languages.vb



Show quoteHide quote

Hi Frank,

Thanks for your post.

Mike and Bill are right. This question about VB.NET. The best place to ask
this question is at microsoft.public.dotnet.languages.vb.

Regarding the attributes, there shouldn't be any problem. All the three
attributes come up from .NET 1.1. You should safely use them in VS.NET 2003.

Please test it in VS.NET 2003 and if there is any issue, report it at
microsoft.public.dotnet.languages.vb. Thanks for your cooperation.

Regards,
Hongye Sun (hong***@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msd***@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/en-us/subscriptions/aa948868.aspx#notifications.

Note: MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within?2 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions. Issues of this
nature are best handled working with a dedicated Microsoft Support Engineer
by contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/en-us/subscriptions/aa948874.aspx
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

   Not marketing .Net in non-.Net groups would
be a good start. Clearly it's your job to be
cloyingly solicitous to people who pay for service,
but you can still do that without disrespecting
the newsgroup.

Creating a reasonable migration path from VB6 would be an even better start.
Releasing a "real" VB 7.0 would surpass that.

I second that Bob, although no one really wants to hear that do they.

I don't usually bother to get involved in these migration "discussions"
anymore as the real issues seem to be totally ignored outside of the
VB-classic community, and the people/companies who are suffering are
flagrantly misrepresented as being somehow dumb

Maybe I should ask a Microsoft consultant how much it would cost to have
someone come in and re-architect nearly a million lines of multi-tier
multi-threaded VB-classic code, and QA it properly, and document the new
product (because it can't be the same), and then organise a switch-over of
our customers from old to new product - while supporting both types of
customer installation in the interim.

    Tony Proctor

Show quoteHide quote

PaintPicture
My concept for a very basic stripboard layouter in VB6
Put Date/Time on Right Side of Form.Caption
Option buttons become black - no text shown
Procedure limit for Form?
Where to store database login information in VB6
Days and Years - Data Comparing
ActiveX Control Crashes - VB6
config file
Is one color brighter than the other one?