Re: Deploying multiple EXE's using the basic publish mechanism of

Thanks for your patience and responses. Sorry for the delay in getting back to you.

I finally pinned down what I could do to at least get the build to work (if not the publish)

I unchecked Enable clickonce security in all the projects that I wanted to reference in the man project. This allowed things to build perfectly.

Now I've got another problem!

If I try to do a build, even one to a local drive, I get a cannot find file error - sound familiar?

This time, it's for a referenced project manifest.

Of course it doesn't exist, unless somebody creates it. And I have no intention of separately publishing the referenced projects.

Besides that, when I did attempt to publish a referenced project publishing turned the Enable click once security option back on! So I can't even build to run in debug mode until I go through and uncheck them all.

And just to be sure, I went through and made sure that all the projects were published to a local hard drive (which according to the KB article from Last December that I keep referencing is the way to do it.) HASN'T MS COME UP WITH A FIX YET for the problem described on that page?

And all of this is all the more painful because some ridiculous design decision and or bug disables the publish now button on the main project every time problems arise. I have to close that window and reopen the project. Not nice.

EUREKA!

Steps to reproduce the problem

1. Create a blank solution
2. Add two VB windows apps.
3. Set APP 1 to start
4. Reference APP 2 in APP1 via the project tab, not the browse tab.
5. Run - it works
6. Click on enable click once security settings in the Project Security tab for APP 2.
7. Attempt to run - APP 1 won't build. Gets error discussed in the KB article I keep mentioning.
8. Go through and set publish site to a local hard drive.
9. Remove enable check marks on security tab.
10. Publish.
11. Observe that the check marks come back - MS WHAT THE (&I^(*&^( DOES CLICK ONCE SECURITY HAVE TO DO WITH PUBLISHING TO A HARD DRIVE????? (Deadlines are getting closer, tempers are getting shorter!-))))
12. Oh yes and notice that you can't publish successfully because the manifest is missing.. Yeah right.
13. Take check marks off and try to run. THings will work.

I've been doing all this in debug configuration. On the oft chance that it made a difference, i changed to release configuration. No difference.

On the oft chance that the refactor add in was screwing things up (it's the only add in.) I unchecked it. Made no difference. Microsoft Update shows no updates. I'm using VSTS for Developers 2005 as issued through MSDN to Certified Partners / ISV Competency.

I can get by for a few days with the fix that allows me to build. HOWEVER, I"m trying to convince the powers to be that publishing via ClickOnce is the way to go. That's a bit difficult when the tools don't work correctly.

There is a work around involving using the browse tab to make the references and linking in all the doco and data by hand, but given the number of different deliverable top level projects that gets old in a hurray. You folk continue to insist that it should work using the projects tab. Let's see that that happens.

Suggestions on what to do will be most appreciated. Not using ClickOnce is not acceptable. I've premised a whole bunch of stuff on it working correctlly.

One other possibility occurs to me. I wasted a huge amount of time trying to track down why I didn't see Configuration Manager in VSTS. Turned out there was an obscure, at leat to me, option set the wrong way. Is there a possibility of that here???

Regards,
Al Christoph

"Kevin Yu [MSFT]" <v-kevy@xxxxxxxxxxxxxxxxxxxx> wrote in message news:ymBAroAzGHA.396@xxxxxxxxxxxxxxxxxxxxxxxx
Hi Al,

As you can see from the KB article, this is a known issue in VB.NET 2005.
Currently I have no better idea than the workaround provided by the KB
article.

If this has business impact to you, I suggest you contact Microsoft PSS on
this issue. You can give them the KB article and state the business impact
to see if they can workout a hotfix for you. Here are their contact info.
Sorry for the inconvenience.

http://support.microsoft.com/common/international.aspx?rdpath=gp;en-us;offer
prophone

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)


.