I saw someone had posted a question about this already, and there were no 
responses. So I am hoping that this will get some. We had problems with the 
previous version of DW.NET 1.5 + VS2003 when attempting to deploy 
applications via a web server. So many problems that we eventually decided 
to run off a network drive (which is OK if your user base doesn't roam 
around the country). Anyway, we gave up on DW.NET, and started to use the 
datagrid control.

Since then, much has changed. Our development team now has VS2005 
professional and may start using DW.NET 2.0 (pending my investigations). So 
here is the situation so far:

VS2005 has an extremely easy to use project deployment/publishing tool. Our 
current set of ClickOnce apps work without problems (as you can expect).

When I place a datawindow control on a winform, and deploy it to a web 
server, it works only if the Sybase DW product has been installed (I can 
sort of see why). My questions:

1) Is there a way to auto deploy a winform app that has a datawindow on it 
so that it auto installs/auto registers any libraries it may need?
2) Are there any tips for how to deploy click once applications? (eg: advice 
on library deployment, and path to PBL's/PBD's from a click once app)
3) Has anyone actually done this? Is it even possible? Is there any 
doco/steps/how-tos on this? The Sybase DW.NET help doesn't mention this 
deployment style specifically. 

I imagine the toughest part would be the unmanaged code:

http://infocenter.sybase.com/help/topic/com.sybase.help.dwnet_2.0.dwprgnet/html/dwprgnet/BABJIEHA.htm

You would need to create a directory on the client to install the
files in and an environmental variable that points to that location.

On 17 Aug 2006 00:46:54 -0700, "JC" <jc@spam.me.not> wrote:

>I saw someone had posted a question about this already, and there were no 
>responses. So I am hoping that this will get some. We had problems with the 
>previous version of DW.NET 1.5 + VS2003 when attempting to deploy 
>applications via a web server. So many problems that we eventually decided 
>to run off a network drive (which is OK if your user base doesn't roam 
>around the country). Anyway, we gave up on DW.NET, and started to use the 
>datagrid control.
>
>Since then, much has changed. Our development team now has VS2005 
>professional and may start using DW.NET 2.0 (pending my investigations). So 
>here is the situation so far:
>
>VS2005 has an extremely easy to use project deployment/publishing tool. Our 
>current set of ClickOnce apps work without problems (as you can expect).
>
>When I place a datawindow control on a winform, and deploy it to a web 
>server, it works only if the Sybase DW product has been installed (I can 
>sort of see why). My questions:
>
>1) Is there a way to auto deploy a winform app that has a datawindow on it 
>so that it auto installs/auto registers any libraries it may need?
>2) Are there any tips for how to deploy click once applications? (eg: advice 
>on library deployment, and path to PBL's/PBD's from a click once app)
>3) Has anyone actually done this? Is it even possible? Is there any 
>doco/steps/how-tos on this? The Sybase DW.NET help doesn't mention this 
>deployment style specifically. 
>

Question...

during the 'click once' process, are you able to install or run msi files on 
the client machine... the reason I ask is, I just recently released an 
application into 'a test' production - 6 beta users - and the install 
process was this...

- check for .net 2 frame work....if not there, run the 2.0 framework update.

- run the msi for registring the Sybase datawindow control...

- copy the exe's and pbl's to the application's folder...

we released it to 6 test users work stations...the above was a manual 
process but completed by the user.

now I am tasked to automate this ... which is not an issue ... as the Sybase 
control has an MSI file that runs and the user simply clicks clicks clicks 
done and the dw control is there ... and the user only has to do this 
once...

now I am free to push out updates to the clients without requiring them to 
even know...simple copy new program and pbl's to application folder ...done.

So, if the click once can check for installed apps (.net 2 framework and / 
or the Sybase control) and if the click once can run other exe's and msi's 
during the deployment, you should be able to do this...

If not, roll your own click-once...for the initial install...then rely on 
MS's click once to update your application files and pbl's ...

Jeff.




"JC" <jc@spam.me.not> wrote in message news:44e41c9e@forums-2-dub...
>I saw someone had posted a question about this already, and there were no 
>responses. So I am hoping that this will get some. We had problems with the 
>previous version of DW.NET 1.5 + VS2003 when attempting to deploy 
>applications via a web server. So many problems that we eventually decided 
>to run off a network drive (which is OK if your user base doesn't roam 
>around the country). Anyway, we gave up on DW.NET, and started to use the 
>datagrid control.
>
> Since then, much has changed. Our development team now has VS2005 
> professional and may start using DW.NET 2.0 (pending my investigations). 
> So here is the situation so far:
>
> VS2005 has an extremely easy to use project deployment/publishing tool. 
> Our current set of ClickOnce apps work without problems (as you can 
> expect).
>
> When I place a datawindow control on a winform, and deploy it to a web 
> server, it works only if the Sybase DW product has been installed (I can 
> sort of see why). My questions:
>
> 1) Is there a way to auto deploy a winform app that has a datawindow on it 
> so that it auto installs/auto registers any libraries it may need?
> 2) Are there any tips for how to deploy click once applications? (eg: 
> advice on library deployment, and path to PBL's/PBD's from a click once 
> app)
> 3) Has anyone actually done this? Is it even possible? Is there any 
> doco/steps/how-tos on this? The Sybase DW.NET help doesn't mention this 
> deployment style specifically.
> 

Well, the problem is:

"Additionally, if an application needs privileged access to the local
machine at install time, then it is definitely not a candidate for
ClickOnce deployment because by design there are no mechanisms in
ClickOnce to add registry entries, install shared assemblies in the
Global Assembly Cache (GAC), install services, and so on."

http://msdn.microsoft.com/msdnmag/issues/04/05/ClickOnce/

However:

http://www.softinsight.com/bnoyes/PermaLink.aspx?guid=2d39e57c-831b-466a-a666-a0839f9eab70

http://www.code-magazine.com/article.aspx?quickid=0601041&page=2

So it's not so much the unmanaged code that is an issue, but creating
the environmental variable needed to tell DataWindow.Net where it's
at.





On 17 Aug 2006 16:25:17 -0700, "jeff" <jhersey at allnorth dottt com>
wrote:

>Question...
>
>during the 'click once' process, are you able to install or run msi files on 
>the client machine... the reason I ask is, I just recently released an 
>application into 'a test' production - 6 beta users - and the install 
>process was this...
>
>- check for .net 2 frame work....if not there, run the 2.0 framework update.
>
>- run the msi for registring the Sybase datawindow control...
>
>- copy the exe's and pbl's to the application's folder...
>
>we released it to 6 test users work stations...the above was a manual 
>process but completed by the user.
>
>now I am tasked to automate this ... which is not an issue ... as the Sybase 
>control has an MSI file that runs and the user simply clicks clicks clicks 
>done and the dw control is there ... and the user only has to do this 
>once...
>
>now I am free to push out updates to the clients without requiring them to 
>even know...simple copy new program and pbl's to application folder ...done.
>
>So, if the click once can check for installed apps (.net 2 framework and / 
>or the Sybase control) and if the click once can run other exe's and msi's 
>during the deployment, you should be able to do this...
>
>If not, roll your own click-once...for the initial install...then rely on 
>MS's click once to update your application files and pbl's ...
>
>Jeff.
>
>
>
>
>"JC" <jc@spam.me.not> wrote in message news:44e41c9e@forums-2-dub...
>>I saw someone had posted a question about this already, and there were no 
>>responses. So I am hoping that this will get some. We had problems with the 
>>previous version of DW.NET 1.5 + VS2003 when attempting to deploy 
>>applications via a web server. So many problems that we eventually decided 
>>to run off a network drive (which is OK if your user base doesn't roam 
>>around the country). Anyway, we gave up on DW.NET, and started to use the 
>>datagrid control.
>>
>> Since then, much has changed. Our development team now has VS2005 
>> professional and may start using DW.NET 2.0 (pending my investigations). 
>> So here is the situation so far:
>>
>> VS2005 has an extremely easy to use project deployment/publishing tool. 
>> Our current set of ClickOnce apps work without problems (as you can 
>> expect).
>>
>> When I place a datawindow control on a winform, and deploy it to a web 
>> server, it works only if the Sybase DW product has been installed (I can 
>> sort of see why). My questions:
>>
>> 1) Is there a way to auto deploy a winform app that has a datawindow on it 
>> so that it auto installs/auto registers any libraries it may need?
>> 2) Are there any tips for how to deploy click once applications? (eg: 
>> advice on library deployment, and path to PBL's/PBD's from a click once 
>> app)
>> 3) Has anyone actually done this? Is it even possible? Is there any 
>> doco/steps/how-tos on this? The Sybase DW.NET help doesn't mention this 
>> deployment style specifically.
>> 
>

Thanks for the response. In the past, I got our support staff to modify the 
..Net framework run-time security policies to fully trust the Sybase 
assemblies. If this trust is in place when the click once application is 
executed, I would assume that the click once application would work.

Jeff indicated that we will need to build an MSI package that contains the 
necessary Sybase DLLs. Our sys admins tell me that we should be able to 
deploy these via a number of auto-install technologies (example: Active 
Directory Group Policies and/or SMS), and have the auto-installer configure 
the run-time security policy. I am hoping that someone out there has 
actually done this (so I can avoid the time wastage associated with trying 
something that won't work).

The PBL may not need an environment variable. In VS 2005, windows forms have 
a flexible settings system (example: dw.LibraryList = My.Settings.PBLPath). 
I think that we may be able to use this to overcome the need to install 
registry entries. It's an XML file that gets deployed by the clickonce 
application.


"Bruce Armstrong [TeamSybase]" <NOCANSPAMbruce.armstrong@teamsybase.com> 
wrote in message news:892ae25dtcs8oqv0b9c3envhpdthtbj044@4ax.com...
>
> Well, the problem is:
>
> "Additionally, if an application needs privileged access to the local
> machine at install time, then it is definitely not a candidate for
> ClickOnce deployment because by design there are no mechanisms in
> ClickOnce to add registry entries, install shared assemblies in the
> Global Assembly Cache (GAC), install services, and so on."
>
> http://msdn.microsoft.com/msdnmag/issues/04/05/ClickOnce/
>
> However:
>
> http://www.softinsight.com/bnoyes/PermaLink.aspx?guid=2d39e57c-831b-466a-a666-a0839f9eab70
>
> http://www.code-magazine.com/article.aspx?quickid=0601041&page=2
>
> So it's not so much the unmanaged code that is an issue, but creating
> the environmental variable needed to tell DataWindow.Net where it's
> at.
>
>
>
>
>
> On 17 Aug 2006 16:25:17 -0700, "jeff" <jhersey at allnorth dottt com>
> wrote:
>
>>Question...
>>
>>during the 'click once' process, are you able to install or run msi files 
>>on
>>the client machine... the reason I ask is, I just recently released an
>>application into 'a test' production - 6 beta users - and the install
>>process was this...
>>
>>- check for .net 2 frame work....if not there, run the 2.0 framework 
>>update.
>>
>>- run the msi for registring the Sybase datawindow control...
>>
>>- copy the exe's and pbl's to the application's folder...
>>
>>we released it to 6 test users work stations...the above was a manual
>>process but completed by the user.
>>
>>now I am tasked to automate this ... which is not an issue ... as the 
>>Sybase
>>control has an MSI file that runs and the user simply clicks clicks clicks
>>done and the dw control is there ... and the user only has to do this
>>once...
>>
>>now I am free to push out updates to the clients without requiring them to
>>even know...simple copy new program and pbl's to application folder 
>>...done.
>>
>>So, if the click once can check for installed apps (.net 2 framework and /
>>or the Sybase control) and if the click once can run other exe's and msi's
>>during the deployment, you should be able to do this...
>>
>>If not, roll your own click-once...for the initial install...then rely on
>>MS's click once to update your application files and pbl's ...
>>
>>Jeff.
>>
>>
>>
>>
>>"JC" <jc@spam.me.not> wrote in message news:44e41c9e@forums-2-dub...
>>>I saw someone had posted a question about this already, and there were no
>>>responses. So I am hoping that this will get some. We had problems with 
>>>the
>>>previous version of DW.NET 1.5 + VS2003 when attempting to deploy
>>>applications via a web server. So many problems that we eventually 
>>>decided
>>>to run off a network drive (which is OK if your user base doesn't roam
>>>around the country). Anyway, we gave up on DW.NET, and started to use the
>>>datagrid control.
>>>
>>> Since then, much has changed. Our development team now has VS2005
>>> professional and may start using DW.NET 2.0 (pending my investigations).
>>> So here is the situation so far:
>>>
>>> VS2005 has an extremely easy to use project deployment/publishing tool.
>>> Our current set of ClickOnce apps work without problems (as you can
>>> expect).
>>>
>>> When I place a datawindow control on a winform, and deploy it to a web
>>> server, it works only if the Sybase DW product has been installed (I can
>>> sort of see why). My questions:
>>>
>>> 1) Is there a way to auto deploy a winform app that has a datawindow on 
>>> it
>>> so that it auto installs/auto registers any libraries it may need?
>>> 2) Are there any tips for how to deploy click once applications? (eg:
>>> advice on library deployment, and path to PBL's/PBD's from a click once
>>> app)
>>> 3) Has anyone actually done this? Is it even possible? Is there any
>>> doco/steps/how-tos on this? The Sybase DW.NET help doesn't mention this
>>> deployment style specifically.
>>>
>>
> 

On 24 Aug 2006 23:14:57 -0700, "JC" <jc@spam.me.not> wrote:

>The PBL may not need an environment variable. In VS 2005, windows forms have 
>a flexible settings system (example: dw.LibraryList = My.Settings.PBLPath). 
>I think that we may be able to use this to overcome the need to install 
>registry entries. It's an XML file that gets deployed by the clickonce 
>application.

Just to clarify, I never said that the PBL needed an environmental
variable.  I said that DataWindow.Net looked for one in order to find
the unmanaged DLLs.