Warning MSB3331

Hot Topic

Control.DataBindings
Please… urgent help about the BeforeNavigation2
WebBrowser background colour / border
auto compelete textbox in win forms vb.net
how to reposition my user controls over a web page
Extender Provider
MenuStrip, ToolStrip and Forms Design Questions?
Send encrypted email
Datagrid basic property help
Problem creating dynamic reports

Windows Forms

ListView column order confusion
BindingContext..EndCurrentEdit() problems
Supporting a Proxy Server/Firewall
First time call ToolTip.Show() in balloon mode places tip pointer at wrong position
Settings - user.config naming?
Docking a form into another one
Getting Extended System Colours
DataGridView Binding
Deployment error vb .net
.NET Label not Refresh()'ing

Warning MSB3331

I have a Windows VB application built using VS 2005 Beta 2 that includes a reference to DAO (3.6) but when I do a build I get the following warning. I can't find information on the warning in MSDN or google. Can anyone explain what is causing this and how to correct it.

=============================
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets : warning MSB3331: Unable to apply publish properties for item "dao".
=============================



Answer this question

Warning MSB3331

  • pneumahagion777

    Can you please turn on verbose logging and send us the snippet of the log that includes the error To enable verbose logging on the command line add a /v:d to the command-line. Inside Visual Studio follow the steps at http://blogs.msdn.com/msbuild/archive/2005/09/29/475157.aspx and set it to "diagnostic".

    Send the message to msbuild@microsoft.com.

    Thanks,

    Neil

  • tovvenki

    Using the Reset All under Application Files also worked for me.



  • odinlai

    Based on the log that we received, this appears to be a problem with the ClickOnce features in build. The "ClickOnce and Deployment" team best understands that part of build, so I'm moving the post to their forum. I will also follow up with them internally so they are aware of this post and can work on investigating the cause.

    Neil

  • GertGregers

    Wayne,

    Are you trying to publish your application using the Publish menu item, or is this a plain build

    Neil

  • csenthil

    This helped me as well, I had the same error but with a custom assembly that I had renamed and couldn't figure out how to fix it. I went into the Publish tab on project properties, clicked Application Files --> Reset All and the error went away. It was just an annoyance but it's nice to have it gone. Thanks.

  • Ken Adams

    This warning tends to come up when the BuildAction or CopyLocal property for the file isn't quite right. For files, BuildAction should probably be "Content"; CopyLocal should probably be "True". Not sure if either of these resolved this particular dao issue, though.

  • Bipul

    Is this issue resolved

    I cannot find any resolution or further correspondance in Click Once forum,

    Can you please post the link if you have it

    Thank you



  • OX

    I have an xsx file that seems to relate to an xsd file. I need to include both in my applicaiton.

    I can include the xsd in my visual studio solution but when I try to add th xsx it doesn't appear to get added; yet it is in the source safe explorer.

    I need to have this file deploy with my click once application since it is needed for an editor component piece in the application. It uses the actipro script editor and I need the language definiton files so the editor can recognize xml syntax and other languages and highlight them appropriately.

    I get this same warning/error for what seems to be the xsx file since that is the only file that does not get created when the application is published; there is not .deploy file for it.

    I made sure the build action is content for all laguage xml files and set the copy to putput directopry as content.

    How do I ensure this xsx file will get properly deployed with my application


  • Link8312

    I sent that snippet

  • kodiya

    No, this happens when I do a normal rebuild.

  • Warning MSB3331
Answer this question