Anybody having problems with VS2005 SP1?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Matthew Etter - 19 Oct 2006 20:59 GMT

We had our first report today from a trial version user that could not use
our VSIP packages under VS2005 with the beta of SP1 installed.
Before I go off and install this beta, has anyone else experimented with it?
Are there known problems with 3rd party packages and the beta of SP1?

Thanks,
Matthew @ SlickEdit

Reply to this Message

Jack Robertson - 19 Oct 2006 23:13 GMT

> We had our first report today from a trial version user that could not use
> our VSIP packages under VS2005 with the beta of SP1 installed.
> Before I go off and install this beta, has anyone else experimented with
> it? Are there known problems with 3rd party packages and the beta of SP1?

While I'm not working with VSIP (extensibility model only), I have had the
beta installed since day one and I've had no issues. In fact, some of the
general problems I had previously are fixed now (unrelated to
extensibility). That may be little comfort for you however since it doesn't
address your VSIP issue per se.

Reply to this Message

Gary Chang[MSFT] - 20 Oct 2006 04:37 GMT

Hi Matthrew,

This is a quick note to let you know that I am performing research on this
issue and will get back to you as soon as possible. I will consult with our
product team to check whether there is any known issue. I appreciate your
patience.

Thanks for your understanding.

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 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 or complex
project analysis and dump analysis issues. 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/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Matthew Etter - 20 Oct 2006 14:11 GMT

I went ahead and installed SP1 Beta on a non-development system, and I
wasn't able to reproduce the customer's error. But I was installing the SP
over top of an installation that already had our packages installed. The
customer had the problem after installing our product after the service pack
was already applied. I'll have to try to reproduce that scenario.
Please don't go off on a wild goose chase on my account :-) I'll post back
if I find anything worth worrying about.

--Matthew

> Hi Matthrew,
>
[quoted text clipped - 29 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Reply to this Message

Gary Chang[MSFT] - 23 Oct 2006 07:04 GMT

Hi Mathew,

I have already forwarded this issue to our product team, the following is
that team lead's reply:

We've heard of only one other VSIP package having an issue with SP1. We
have no details at the present time and the supplier of the package did not
have a repro, just a customer report. They are investigating now.

This is the first we've heard of a problem with SlickEdit. We highly
suugest SlickEdit needs to try this out and file a bug on msdn connect as
soon as possible with appropriate details like a call stack. Once we have
a bug filed, then we should be able to expedite its treatment to determine
if the SP1 fix affecting their functionality needs to be reconsidered. The
bar is very high on SP1 already so we need to move quickly.

Our product team will communicate with you directly on the issue in the
MSDN Connect :

http://connect.microsoft.com/site/sitehome.aspx?SiteID=210

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Mirko Matytschak - 07 Nov 2006 10:12 GMT

Yes, one of our customers has reported an error in an Add-in with the
following message:

"Attempted to read or write protected memory. This is often an indication
that other memory is corrupt."

Our Add-in is essentially a user interface which launches external programs.
It adds a toolbar and some menu items to VS. It also iterates throug the
solution tree to identify the members of the projects in the solution. So it
seems as if there is a severe change in the named areas.

I didn't find a download location for SP 1 to reproduce the error - is there
a way for universal subscribers to download a beta?

Regards:
Mirko Matytschak

> We had our first report today from a trial version user that could not use
> our VSIP packages under VS2005 with the beta of SP1 installed.
[quoted text clipped - 3 lines]
> Thanks,
> Matthew @ SlickEdit

Reply to this Message

Anybody having problems with VS2005 SP1?

Free Magazines