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 / IDE / June 2006

Tip: Looking for answers? Try searching our database.

Satellite assemblies could not be built because the main project output is missing

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
mjs@community.nospam - 26 Jun 2006 13:28 GMT
I'm sorry if this has already been asked before but I have a problem that
has only just started to happen.

When I first open a particular project it compiles and runs as expected.
However when I return to the IDE and try to F5(Debug), rebuild again I get
the following message

------ Build started: Project: App01, Configuration: Debug .NET ------

Preparing resources...
Updating references...
Performing main compilation...
Building satellite assemblies...
Satellite assemblies could not be built because the main project output is
missing.

---------------------- Done ----------------------

   Build: 0 succeeded, 1 failed, 0 skipped

    Any ideas?

    Mark
"Gary Chang[MSFT]" - 27 Jun 2006 07:20 GMT
Hi Mark,

Thank you posting!

Does this problem occur when you build a Visual C# solution in Visual
Studio .NET 2003?

If so, I am afraid this is known product issue in VS2003. Currently there
is a supported hotfix available from Microsoft, but it is only intended to
correct the problem that is described in this article.

To resolve this problem immediately, contact Microsoft Product Support
Services to obtain the hotfix. For a complete list of Microsoft Product
Support Services telephone numbers and information about support costs,
visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Please refer to the following MSDN KB article for the detailed information:

http://support.microsoft.com/?kbid=867770

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
mjs@community.nospam - 27 Jun 2006 09:59 GMT
Gary

Thanks for the reply.

I should have made my issue clear at the beginning, but here goes:

I'm using VS2003

The project is VB.NET and not C# etc

I have been working in the project for a few months now so the project now
has approximately:

14 Forms
20 Dialogs
29 Datasets
35 Crystal Reports
15 Classes/modules

I don't know if that amount of items is considered large for a single
project, but the behaviour that I have described has only just stared to
happen (last 4-5 days)

I have tried rolling back to a previous version of the project that was
saved last week.  It behaves correctly.  I will examine the differences
between the two versions and bring the saved version in to line with the
current one.  Hopefully the behaviour won't happen this time, or at least I
will figure out which addition causes the problem.

However, any help you can give me will be greatly appreciated

B.T.W. Will the C# hotfix work for VB projects?

Many thanks

Mark

> Hi Mark,
>
[quoted text clipped - 31 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"Gary Chang[MSFT]" - 28 Jun 2006 04:22 GMT
Hi Mark,

>I have tried rolling back to a previous version of the
>project that was saved last week.  It behaves correctly.
> I will examine the differences between the two versions
>and bring the saved version in to line with the current one.
>Hopefully the behaviour won't happen this time, or at least
>I will figure out which addition causes the problem.

yes, there may be some modification caused this issue. I wish you can find
the root cause.

By the way, for the issue about that hotfix, I suggest you can try the
command line build ("This problem does not occur if you use the Devenv
/build command-line command to build the solution") to your VB.NET project.
If this problem is caused by that KB specific bug, your project would be
built successfully with command line.

Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

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.