Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Extensibility / July 2004

Tip: Looking for answers? Try searching our database.

Whidbey Beta 1

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Gaston Milano - 05 Jul 2004 15:07 GMT
After I installed whidbey beta 1, I can't run my VSIP projects compiled
using the debug configuration  anymore. The problem is that the projects are
linked to vsassert.dll that is on window\system32 and this dll after install
whidbey is depending on msvcr80.dll.
Where can i find the old vsassert.dll ? Could somebody send me this file?
(before install whidbey :)
Is it a bug of whidbey setup?

Regards,
Gaston Milano
Michael He - 07 Jul 2004 02:13 GMT
> After I installed whidbey beta 1, I can't run my VSIP projects compiled
> using the debug configuration  anymore. The problem is that the projects are
[quoted text clipped - 6 lines]
> Regards,
> Gaston Milano

Same problem here...
Frank Boyne - 07 Jul 2004 23:50 GMT
> After I installed whidbey beta 1, I can't run my VSIP projects compiled
> using the debug configuration  anymore.

This (from microsoft.public.vsnet.general and
microsoft.public.vsnet.vsip) might help...

"Thomas Scheidegger [MVP]" <spam.netmaster@swissonline.ch>
wrote in message
news:u%23vF9dIYEHA.3300@TK2MSFTNGP09.phx.gbl...
> just seen at MS-download:
>
> VSIP SDK 2005 Beta 1

http://www.microsoft.com/downloads/details.aspx?familyid=94c9970d-c247-4ded-a76d
-f7b3d589e71d


http://download.microsoft.com/download/6/9/5/69552ee5-3c00-44b7-935c-b32497db165
8/VSIP05B1DL.EXE


> http://msdn.microsoft.com/vstudio/extend/
Gaston Milano - 08 Jul 2004 13:24 GMT
I found the vsassert.dll in another machine I uploaded the vsassert.dll

http://weblogs.asp.net/gmilano/archive/2004/07/07/175707.aspx

Regards,
Gaston

> After I installed whidbey beta 1, I can't run my VSIP projects compiled
> using the debug configuration  anymore. The problem is that the projects are
[quoted text clipped - 6 lines]
> Regards,
> Gaston Milano
Rick Strahl [MVP] - 09 Jul 2004 22:50 GMT
No problem for me on my Whidbey install machine... It looks like Whidbey
didn't touch my vsassert.dll at all...

+++ Rick ---

Signature

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
----------------------------------
Making waves on the Web

> After I installed whidbey beta 1, I can't run my VSIP projects compiled
> using the debug configuration  anymore. The problem is that the projects are
[quoted text clipped - 6 lines]
> Regards,
> Gaston Milano
R. Brian Lindahl - 19 Jul 2004 17:12 GMT
Same problem here... with new dll, dated 6/24/2004, i can't run regsvr32 on
the 2003 packages - "module not found". i don't see a dependency on msvcr80
with the dependency checker i'm using, however, i don't have msvcr80... only
msvcr80d.

Signature

R. Brian Lindahl [RemObjects Software]

> After I installed whidbey beta 1, I can't run my VSIP projects compiled
> using the debug configuration  anymore. The problem is that the projects are
[quoted text clipped - 6 lines]
> Regards,
> Gaston Milano

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.