clickonce deployment is fucked

Error 1 Publish failed with the following error: Could not find a part of
the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.

:( Its not even building anything to that directory...I cant change it...I
could try placing my build in that directory but thats fucked? clickonce my
ass...

I've tried rebuilding all
I've tried using the publish button from the project properties
I've tried using the context menu publish
I've looked through all the options 100 times...(ok well 3 or 4 times)

wtf man...

Sorry Im frustrated...any ideas would be very muchly appreciated..thank you.
John

Re: clickonce deployment is fucked

Are you still having this problem, or did you figure it out?

RobinS.
GoldMail, Inc.
---------------------
"John Sheppard" wrote in message
news:fka6oa0abi@news2.newsguy.com...
> Error 1 Publish failed with the following error: Could not find a part of
> the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.
>
> :( Its not even building anything to that directory...I cant change it...I
> could try placing my build in that directory but thats fucked? clickonce
> my ass...
>
> I've tried rebuilding all
> I've tried using the publish button from the project properties
> I've tried using the context menu publish
> I've looked through all the options 100 times...(ok well 3 or 4 times)
>
> wtf man...
>
> Sorry Im frustrated...any ideas would be very muchly appreciated..thank
> you.
> John

Re: clickonce deployment is fucked

On Dec 18 2007, 9:30=A0pm, "John Sheppard" wrote:
> clickonce my
> ass...

LOL...
i'm sorry ... i don't mean to laugh, but that's funny.

Re: clickonce deployment is fucked

Couldnt figure it out... :( So I've given up...and reverted to a normal
deployment...it sucks...but its easier, from my research clickonce all seams
like a nightmare anyway...seams like one of the microsoft things that isnt
really thought out/developed correctly...

I 'suspect' its something to do with having a webservice project in the same
solution...

If time wasnt an issue id look into it further but for now normal deployment
is the go....I think I might end up rolling my own some time down the future
or seeing how it goes in vs2008 when the time comes...(in 2010) :)

Thanks...
John Sheppard

"RobinS" wrote in message
news:OJOdnXBa2pwCfuDanZ2dnUVZ_uyinZ2d@comcast.com...
> Are you still having this problem, or did you figure it out?
>
> RobinS.
> GoldMail, Inc.
> ---------------------
> "John Sheppard" wrote in message
> news:fka6oa0abi@news2.newsguy.com...
>> Error 1 Publish failed with the following error: Could not find a part of
>> the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.
>>
>> :( Its not even building anything to that directory...I cant change
>> it...I could try placing my build in that directory but thats fucked?
>> clickonce my ass...
>>
>> I've tried rebuilding all
>> I've tried using the publish button from the project properties
>> I've tried using the context menu publish
>> I've looked through all the options 100 times...(ok well 3 or 4 times)
>>
>> wtf man...
>>
>> Sorry Im frustrated...any ideas would be very muchly appreciated..thank
>> you.
>> John
>

Re: clickonce deployment is fucked

Just FYI, my company is successfully using ClickOnce to deploy our product,
GoToMeeting uses it for theirs, and MSFT uses it to deploy their HR software
internally to 75,000 employees. I found Brian Noyes's book about it to be
invaluable.

I've seen this error before. I think I used to get it when I used the
Publish buttons once in a while, and would use the Build/Publish option from
the menu instead. There is a KB article about that on MSDN IIRC.

You also might try deleting your bin directory and doing a Rebuild Solution
and trying again.

If none of that works, is your project small enough to send to me to look
at? I'd be willing to do that for you.

We've been pretty happy with ClickOnce. Our primary motivation for using it
was to get the incremental upgrade capabilities, and it's working well for
us. Sorry you're having so much trouble with it.

RobinS.
GoldMail, Inc.
-----------------------------------

"John" wrote in message
news:fllc2p04be@news5.newsguy.com...
> Couldnt figure it out... :( So I've given up...and reverted to a normal
> deployment...it sucks...but its easier, from my research clickonce all
> seams like a nightmare anyway...seams like one of the microsoft things
> that isnt really thought out/developed correctly...
>
> I 'suspect' its something to do with having a webservice project in the
> same solution...
>
> If time wasnt an issue id look into it further but for now normal
> deployment is the go....I think I might end up rolling my own some time
> down the future or seeing how it goes in vs2008 when the time comes...(in
> 2010) :)
>
> Thanks...
> John Sheppard
>
> "RobinS" wrote in message
> news:OJOdnXBa2pwCfuDanZ2dnUVZ_uyinZ2d@comcast.com...
>> Are you still having this problem, or did you figure it out?
>>
>> RobinS.
>> GoldMail, Inc.
>> ---------------------
>> "John Sheppard" wrote in message
>> news:fka6oa0abi@news2.newsguy.com...
>>> Error 1 Publish failed with the following error: Could not find a part
>>> of the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.
>>>
>>> :( Its not even building anything to that directory...I cant change
>>> it...I could try placing my build in that directory but thats fucked?
>>> clickonce my ass...
>>>
>>> I've tried rebuilding all
>>> I've tried using the publish button from the project properties
>>> I've tried using the context menu publish
>>> I've looked through all the options 100 times...(ok well 3 or 4 times)
>>>
>>> wtf man...
>>>
>>> Sorry Im frustrated...any ideas would be very muchly appreciated..thank
>>> you.
>>> John
>>
>
>

Re: clickonce deployment is fucked

True, it is more like "Click 6 times", especially if you push .Net 2.0 as a
prerequisite! :-)

RobinS.
GoldMail, Inc.
---------------------
"forest demon" wrote in message
news:11fadccb-cb29-4dee-a61d-2dad17909098@e6g2000prf.googleg roups.com...
On Dec 18 2007, 9:30 pm, "John Sheppard" wrote:
> clickonce my
> ass...

LOL...
i'm sorry ... i don't mean to laugh, but that's funny.

Re: clickonce deployment is fucked

Yeah I've seen that alot of people have a similar problem and found that the
context menu on the solution explorer's publish works correctly. I think i
saw that MS KB article in my travels also...

Unfortunatly in my case that didnt seam to work, I have tried a complete
rebuild. What leads me to believe that its something to do with a webservice
being in the same solution (different project) is that when I try to publish
it is trying to publish to where ever my web service was published last. I
cant be specific about it cause it was last week and ive moved on and dont
recall :(, what I can be specific about is that i thought WTF....

Thank you very kindly for your offer of assistance, unfortunatly my boss
would not be real happy about his code being sent off premesis...

When i am free from a hard time schedule I will have another look at it....

"RobinS" wrote in message
news:lp-dnVcln9s_kOLanZ2dnUVZ_umlnZ2d@comcast.com...
>
> Just FYI, my company is successfully using ClickOnce to deploy our
> product, GoToMeeting uses it for theirs, and MSFT uses it to deploy their
> HR software internally to 75,000 employees. I found Brian Noyes's book
> about it to be invaluable.
>
> I've seen this error before. I think I used to get it when I used the
> Publish buttons once in a while, and would use the Build/Publish option
> from the menu instead. There is a KB article about that on MSDN IIRC.
>
> You also might try deleting your bin directory and doing a Rebuild
> Solution and trying again.
>
> If none of that works, is your project small enough to send to me to look
> at? I'd be willing to do that for you.
>
> We've been pretty happy with ClickOnce. Our primary motivation for using
> it was to get the incremental upgrade capabilities, and it's working well
> for us. Sorry you're having so much trouble with it.
>
> RobinS.
> GoldMail, Inc.
> -----------------------------------
>
> "John" wrote in message
> news:fllc2p04be@news5.newsguy.com...
>> Couldnt figure it out... :( So I've given up...and reverted to a normal
>> deployment...it sucks...but its easier, from my research clickonce all
>> seams like a nightmare anyway...seams like one of the microsoft things
>> that isnt really thought out/developed correctly...
>>
>> I 'suspect' its something to do with having a webservice project in the
>> same solution...
>>
>> If time wasnt an issue id look into it further but for now normal
>> deployment is the go....I think I might end up rolling my own some time
>> down the future or seeing how it goes in vs2008 when the time comes...(in
>> 2010) :)
>>
>> Thanks...
>> John Sheppard
>>
>> "RobinS" wrote in message
>> news:OJOdnXBa2pwCfuDanZ2dnUVZ_uyinZ2d@comcast.com...
>>> Are you still having this problem, or did you figure it out?
>>>
>>> RobinS.
>>> GoldMail, Inc.
>>> ---------------------
>>> "John Sheppard" wrote in message
>>> news:fka6oa0abi@news2.newsguy.com...
>>>> Error 1 Publish failed with the following error: Could not find a part
>>>> of the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.
>>>>
>>>> :( Its not even building anything to that directory...I cant change
>>>> it...I could try placing my build in that directory but thats fucked?
>>>> clickonce my ass...
>>>>
>>>> I've tried rebuilding all
>>>> I've tried using the publish button from the project properties
>>>> I've tried using the context menu publish
>>>> I've looked through all the options 100 times...(ok well 3 or 4 times)
>>>>
>>>> wtf man...
>>>>
>>>> Sorry Im frustrated...any ideas would be very muchly appreciated..thank
>>>> you.
>>>> John
>>>
>>
>>
>

Re: clickonce deployment is fucked

Okay, good luck with that. I also have an acct with GoToMeeting we could
use, so
if you ever DO come back around and want to see what's wrong with it, post
back
and if I'm around, I'll see what I can do.

Good luck.

RobinS.
GoldMail, Inc.
-----------------------------
"John" wrote in message
news:flo62f025v5@news4.newsguy.com...
> Yeah I've seen that alot of people have a similar problem and found that
> the context menu on the solution explorer's publish works correctly. I
> think i saw that MS KB article in my travels also...
>
> Unfortunatly in my case that didnt seam to work, I have tried a complete
> rebuild. What leads me to believe that its something to do with a
> webservice being in the same solution (different project) is that when I
> try to publish it is trying to publish to where ever my web service was
> published last. I cant be specific about it cause it was last week and ive
> moved on and dont recall :(, what I can be specific about is that i
> thought WTF....
>
> Thank you very kindly for your offer of assistance, unfortunatly my boss
> would not be real happy about his code being sent off premesis...
>
> When i am free from a hard time schedule I will have another look at
> it....
>
> "RobinS" wrote in message
> news:lp-dnVcln9s_kOLanZ2dnUVZ_umlnZ2d@comcast.com...
>>
>> Just FYI, my company is successfully using ClickOnce to deploy our
>> product, GoToMeeting uses it for theirs, and MSFT uses it to deploy their
>> HR software internally to 75,000 employees. I found Brian Noyes's book
>> about it to be invaluable.
>>
>> I've seen this error before. I think I used to get it when I used the
>> Publish buttons once in a while, and would use the Build/Publish option
>> from the menu instead. There is a KB article about that on MSDN IIRC.
>>
>> You also might try deleting your bin directory and doing a Rebuild
>> Solution and trying again.
>>
>> If none of that works, is your project small enough to send to me to look
>> at? I'd be willing to do that for you.
>>
>> We've been pretty happy with ClickOnce. Our primary motivation for using
>> it was to get the incremental upgrade capabilities, and it's working well
>> for us. Sorry you're having so much trouble with it.
>>
>> RobinS.
>> GoldMail, Inc.
>> -----------------------------------
>>
>> "John" wrote in message
>> news:fllc2p04be@news5.newsguy.com...
>>> Couldnt figure it out... :( So I've given up...and reverted to a normal
>>> deployment...it sucks...but its easier, from my research clickonce all
>>> seams like a nightmare anyway...seams like one of the microsoft things
>>> that isnt really thought out/developed correctly...
>>>
>>> I 'suspect' its something to do with having a webservice project in the
>>> same solution...
>>>
>>> If time wasnt an issue id look into it further but for now normal
>>> deployment is the go....I think I might end up rolling my own some time
>>> down the future or seeing how it goes in vs2008 when the time
>>> comes...(in 2010) :)
>>>
>>> Thanks...
>>> John Sheppard
>>>
>>> "RobinS" wrote in message
>>> news:OJOdnXBa2pwCfuDanZ2dnUVZ_uyinZ2d@comcast.com...
>>>> Are you still having this problem, or did you figure it out?
>>>>
>>>> RobinS.
>>>> GoldMail, Inc.
>>>> ---------------------
>>>> "John Sheppard" wrote in message
>>>> news:fka6oa0abi@news2.newsguy.com...
>>>>> Error 1 Publish failed with the following error: Could not find a part
>>>>> of the path 'C:\Work\sun\sun\bin\Release\sun.publish\sun_1_0_0_0'.
>>>>>
>>>>> :( Its not even building anything to that directory...I cant change
>>>>> it...I could try placing my build in that directory but thats fucked?
>>>>> clickonce my ass...
>>>>>
>>>>> I've tried rebuilding all
>>>>> I've tried using the publish button from the project properties
>>>>> I've tried using the context menu publish
>>>>> I've looked through all the options 100 times...(ok well 3 or 4 times)
>>>>>
>>>>> wtf man...
>>>>>
>>>>> Sorry Im frustrated...any ideas would be very muchly
>>>>> appreciated..thank you.
>>>>> John
>>>>
>>>
>>>
>>
>
>