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 / August 2008

Tip: Looking for answers? Try searching our database.

Rebuild all for debug build with VS.NET 2005 IDE set up for VB development?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andreas Hansson - 15 Aug 2008 15:13 GMT
Hello!

I recently had a problem where I was constantly getting a compile error
saying I had to add a reference to a particular assembly, even though I
already had all the appropriate references. It was resolved for the release
build by doing a Rebuild All. However, I still got the same error message
when attempting to debug the program, and I could not find a way to do a
clean rebuild for the debug build. I even renamed the bin\Debug subdirectory
and that didn't help. I finally went ahead and reset my development settings
to the General Development Settings, then did a rebuild all for the debug
build and problem was gone.

Now what I'm wondering is, did I have to do that? Is there a different way
to resolve that error if it occurs again with the IDE set up for VB
development?

Thanks in advance,
Andreas Hansson
Hongye Sun [MSFT] - 18 Aug 2008 07:08 GMT
Hello Andreas,

Thank you posting!

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 appreciate your
patience.

Regards,
Hongye Sun (hongyes@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:
msdnmg@microsoft.com.

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

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://support.microsoft.com/select/default.aspx?target=assistance&ln=en-us.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Hongye Sun [MSFT] - 18 Aug 2008 11:30 GMT
Hello  Andreas Hansson,

After doing some research on your issue, I am sorry that I could not  
reproduce it and no similar issue found in community. So I suppose this
should be an environment or setting issue.

From your description, I got that after resetting VS.net to General
Development Settings, the build error disappeared.  It looks like this
error is caused by VS.net setting. In order to prove the guess, would you
please to reset the development settings again, and set it back to VB
development settings. The steps are:
1.    Open IDE, open menu item [Tools] / [Importing and Exporting Settings]
2.    Choose "Reset all settings", click Next
3.    Choose to back up your settings and click Next
4.    Choose "Visual Basic Development  Settings" and click Finish
Then please build the project again in debug mode. And check if there is an
error.

If there is no error, that means your original setting is not correct. When
you encounter such issue again, you can reset the development setting to
"Visual Basic Development Settings" instead of "General Development
Settings". It will also reset all the settings to default value.

If the error occurs again, based on the current information, I cannot
locate the real cause. In order to narrow down the problem, would you
please try this:
1.    If you have multiple projects in one solution, please try the following:
"    Use project reference instead of file reference if possible.
"    Delete the broken reference which is reported in the build error and add
it again.
"    Build each project separately from the bottom of the project dependency
tree to the top. And locate which project build is failed while all its
dependent projects are successfully built.
"    Please refer to
http://msdn.microsoft.com/en-us/library/ayds71se(VS.80).aspx for broken
rule troubleshooting.
2.    If the you have only one project, try to create a new project with the
same files and try to build it again. If this way works, that means it is a
project setting issue.

Anyway,  output content is important for us to do troubleshooting. I would
appreciate it if you could collect the information in the output window to
us. You can collect it by:
1.    Open menu item [Tool] / [Options].
2.    In the options window, check "show all settings" at left bottom.
3.    Select [Projects and Solutions] / [Builds and Run] in the left menu.
4.    Select "MSBuild project build output verbosity" to "Diagnostic", and
click ok button.
5.    Open menu item [Debug] / [Windows] / [Output], and you will see the
output window lay on the IDE.
6.    Rebuild the solution again and in the output window you will see the
trace information. If not, please select "Show output from" to "Build".
7.    Click on the content of the output window, and make your cursor focus in
the output window.
8.    Hold [CTRL] and press [A] on keyboard, and make sure all the content in
the output window is selected.
9.    Right click on the selection in output window, and choose copy. Or you
can Hold [CTRL] and press [C].
10.    Open an txt file and paste output into it. Send the txt file to me.

I am looking forward to your update and reply, and please let me know if
there is any additional information that I missed here.

Regards,
Hongye Sun (hongyes@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:
msdnmg@microsoft.com.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Hongye Sun [MSFT] - 20 Aug 2008 10:26 GMT
Hi Andreas,

I would like to follow up on this issue and see if any progress has been
made. I haven't heard from you in 2 days, were you able to check my reply?
Should you have any questions, please feel free to post here.
Looking forward to your reply!

Regards,
Hongye Sun (hongyes@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:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
Andreas Hansson - 20 Aug 2008 12:22 GMT
Hello!

I tried for a while to reproduce the original issue to get you the original
error message, but ever since I did the clean rebuild, the project is
compiling without errors. You suggested removing and readding the relevant
references to fix the error, but I actually tried that before the rebuild
all, and it did not resolve the problem. I think you have misunderstood my
question somewhat. I was asking if there is a way in the VS.NET 2005 IDE to
do a clean rebuild of the debug build of a vb.net application, while using
the development settings for writing vb.net applications, because doing a
clean rebuild of the debug build was what resolved the problem in the end.

What made it take so long for me to resolve the problem was my mistaken
assumption that I could select "Clean Solution" from the Build menu in order
to get a clean build of the executable that is built and executed when I
select "Start Debugging" from the Debug menu. Which proved not to be the
case. It confused me, and so I wanted to know how I am supposed to do a
clean build of the debug build of a project when developing vb applications.
Switching the settings back and forth between vb.net development settings
and general development settings has not changed the behaviour of the
"Clean" or "Clean Solution" options when using the vb development settings;
it still just cleans the release build.

Yours,
Andreas Hansson

> Hi Andreas,
>
[quoted text clipped - 15 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Hongye Sun [MSFT] - 21 Aug 2008 09:06 GMT
Hi Andreas,

Thanks for your reply.

Sorry for my misunderstanding in my last reply. I think I got your concern
this time. You question is: how can you do a clean build of the debug build
of  a project when developing VB application with VB development setting in
VS.NET 2005? If I still misunderstood the question, please correct me.

The cause of your issue is:
In VB development settings, it is designed to maximize the productivity of
Visual Basic developers. So by default, it sets the build configuration in
release mode and hide the build configurations. When you open the property
of the project and switch to Compile tab, you will see that the Build
output path is bin\Release\ and without build configuration settings.

The solution is:
1.    Open Menu Tools / Options, in the Options window, Select Projects and
Solutions / General.
2.    On the right pane, check Show advanced build configurations and click OK
button.
3.    Right click the project file and open its Properties tab.
4.    On the right menu, switch to Compile, you will see Configuration and
Platform on the top of the tab.
5.    Select the Configuration dropdown to debug, and you will see the Build
output path is by default set to bin\Debug\. If it doesn't change, set it
to debug path manually.
Now you can press F5 to try debugging and you can also clean the debug
build now.

Hope it helps.

Regards,
Hongye Sun (hongyes@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:
msdnmg@microsoft.com.

This posting is provided "AS IS" with no warranties, and confers no rights.
Andreas Hansson - 21 Aug 2008 10:36 GMT
Ah, thank you, that option was exactly what I was missing!

After checking that box, I could use the configuration manager in the build
menu to switch to the debug configuration and clean that. Perfect!

Thanks so much,

Andreas Hansson

> Hi Andreas,
>
[quoted text clipped - 43 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Hongye Sun [MSFT] - 25 Aug 2008 09:12 GMT
You are welcome, Andreas.

Have a great day!

Regards,
Hongye Sun (hongyes@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:
msdnmg@microsoft.com.

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.