|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Should I or shouldn't I include excel.exe in my app distribution package?I am confused by the Setup Wizard. I have 2 applications which include Excel automation: (very simple interaction with Excel spreadsheet, mostly just reading data from some cells). When preparing setup package for one application Setup Wizard does not include excel.exe file, but the same Setup Wizard includes excel.exe file with the 2nd application setup package. My questions: 1. Why there is such difference between these 2 applications? 2. Should I include that excel.exe file with my distributable package or not. (MS Office ver.10) 3. If yes to 2) above, do I need MSoft license to do that? Your comments appreciated, Jack
Show quote
Hide quote
"Jack" <replyto@it> wrote in message Does one use late binding and one use early binding? If you have nonews:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl > Hello, > I am confused by the Setup Wizard. > I have 2 applications which include Excel automation: (very simple > interaction with Excel spreadsheet, mostly just reading data from some > cells). > When preparing setup package for one application Setup Wizard does not > include excel.exe file, > but the same Setup Wizard includes excel.exe file with the 2nd > application setup package. > My questions: > 1. > Why there is such difference between these 2 applications? reference to Excel then it won't be found > 2. Absolutely not. You can not redistribute Excel; your target users must have> Should I include that excel.exe file with my distributable package or > not. (MS Office ver.10) it installed already. > 3. If you want to purchase excel licenses and transfer them to the users you> If yes to 2) above, do I need MSoft license to do that? could probably legally install Excel for them. It's not a typical scenario. -- Reply to the group so all can participate VB.Net: "Fool me once..." You should only be distributing the Excel Object model. Not the Application
exe. Show quoteHide quote "Jack" <replyto@it> wrote in message news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... > Hello, > I am confused by the Setup Wizard. > I have 2 applications which include Excel automation: (very simple > interaction with Excel spreadsheet, mostly just reading data from some > cells). > When preparing setup package for one application Setup Wizard does not > include excel.exe file, > but the same Setup Wizard includes excel.exe file with the 2nd application > setup package. > My questions: > 1. > Why there is such difference between these 2 applications? > 2. > Should I include that excel.exe file with my distributable package or not. > (MS Office ver.10) > 3. > If yes to 2) above, do I need MSoft license to do that? > > Your comments appreciated, > Jack > "Brian" <bkstig***@usa.net> wrote in message Not even thatnews:uX8Es$pWHHA.1432@TK2MSFTNGP02.phx.gbl > You should only be distributing the Excel Object model. -- Reply to the group so all can participate VB.Net: "Fool me once..." "Brian" <bkstig***@usa.net>'s wild thoughts were released on Tue, 27 Feb 2007 10:48:49 -0800 bearing the following fruit:>You should only be distributing the Excel Object model. Not the Application The P&DW should only tell you it needs the object model but>exe. > > that is not redistributable either. J Show quoteHide quote >"Jack" <replyto@it> wrote in message >news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... >> Hello, >> I am confused by the Setup Wizard. >> I have 2 applications which include Excel automation: (very simple >> interaction with Excel spreadsheet, mostly just reading data from some >> cells). >> When preparing setup package for one application Setup Wizard does not >> include excel.exe file, >> but the same Setup Wizard includes excel.exe file with the 2nd application >> setup package. >> My questions: >> 1. >> Why there is such difference between these 2 applications? >> 2. >> Should I include that excel.exe file with my distributable package or not. >> (MS Office ver.10) >> 3. >> If yes to 2) above, do I need MSoft license to do that? >> >> Your comments appreciated, >> Jack >> > P&DW
what the animal is that? Jack Show quoteHide quote "Jan Hyde" <StellaDrin***@REMOVE.ME.uboot.com> wrote in message news:tvhau21qsessksjvdilgkv4rjtgdoghnv9@4ax.com... > "Brian" <bkstig***@usa.net>'s wild thoughts were released on > Tue, 27 Feb 2007 10:48:49 -0800 bearing the following fruit: > >>You should only be distributing the Excel Object model. Not the >>Application >>exe. >> >> > > The P&DW should only tell you it needs the object model but > that is not redistributable either. > > J > >>"Jack" <replyto@it> wrote in message >>news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... >>> Hello, >>> I am confused by the Setup Wizard. >>> I have 2 applications which include Excel automation: (very simple >>> interaction with Excel spreadsheet, mostly just reading data from some >>> cells). >>> When preparing setup package for one application Setup Wizard does not >>> include excel.exe file, >>> but the same Setup Wizard includes excel.exe file with the 2nd >>> application >>> setup package. >>> My questions: >>> 1. >>> Why there is such difference between these 2 applications? >>> 2. >>> Should I include that excel.exe file with my distributable package or >>> not. >>> (MS Office ver.10) >>> 3. >>> If yes to 2) above, do I need MSoft license to do that? >>> >>> Your comments appreciated, >>> Jack >>> >> > "Jack" <replyto@it> wrote in message Package and Deployment Wizard. You can run it "Standalone" or as an add-in news:uaxi9X1WHHA.3972@TK2MSFTNGP03.phx.gbl... > P&DW > what the animal is that? > Jack from within VBs IDE. It's a bit out-dated for modern OSs but can be tweaked if you want to spend time, instead of money on a modern installation utility. -- Ken Halter - MS-MVP-VB - Please keep all discussions in the groups.. In Loving Memory - http://www.vbsight.com/Remembrance.htm P&DW = Package & Deployment Wizard
Show quoteHide quote "Jack" <replyto@it> wrote in message news:uaxi9X1WHHA.3972@TK2MSFTNGP03.phx.gbl... > P&DW > what the animal is that? > Jack Too high level for me.
I am still using neat vbasic 5 and Setup Wizard. Jack Show quoteHide quote "Jack" <replyto@it> wrote in message news:uaxi9X1WHHA.3972@TK2MSFTNGP03.phx.gbl... > P&DW > what the animal is that? > Jack > "Jan Hyde" <StellaDrin***@REMOVE.ME.uboot.com> wrote in message > news:tvhau21qsessksjvdilgkv4rjtgdoghnv9@4ax.com... >> "Brian" <bkstig***@usa.net>'s wild thoughts were released on >> Tue, 27 Feb 2007 10:48:49 -0800 bearing the following fruit: >> >>>You should only be distributing the Excel Object model. Not the >>>Application >>>exe. >>> >>> >> >> The P&DW should only tell you it needs the object model but >> that is not redistributable either. >> >> J >> >>>"Jack" <replyto@it> wrote in message >>>news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... >>>> Hello, >>>> I am confused by the Setup Wizard. >>>> I have 2 applications which include Excel automation: (very simple >>>> interaction with Excel spreadsheet, mostly just reading data from some >>>> cells). >>>> When preparing setup package for one application Setup Wizard does not >>>> include excel.exe file, >>>> but the same Setup Wizard includes excel.exe file with the 2nd >>>> application >>>> setup package. >>>> My questions: >>>> 1. >>>> Why there is such difference between these 2 applications? >>>> 2. >>>> Should I include that excel.exe file with my distributable package or >>>> not. >>>> (MS Office ver.10) >>>> 3. >>>> If yes to 2) above, do I need MSoft license to do that? >>>> >>>> Your comments appreciated, >>>> Jack >>>> >>> >> > > "Jack" <replyto@it>'s wild thoughts were released on Wed, 28 Feb 2007 20:43:24 -0500 bearing the following fruit:>Too high level for me. IIRC the 'setup wizard' in VB5 *is* the P&DW.>I am still using neat vbasic 5 and Setup Wizard. If you have the time, look at Inno Setup - free and pretty good. You cannot "distribute" Excel, unless you are MS software reseller. Your
setup package should not include anything from Excel (even the Excel Object Type library). The user has to have Excel (no older version than yours, usually, if you automate Excel using early binding) installed anyway, so he/she would have all files inside Excel on the computer. Show quoteHide quote "Jack" <replyto@it> wrote in message news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... > Hello, > I am confused by the Setup Wizard. > I have 2 applications which include Excel automation: (very simple > interaction with Excel spreadsheet, mostly just reading data from some > cells). > When preparing setup package for one application Setup Wizard does not > include excel.exe file, > but the same Setup Wizard includes excel.exe file with the 2nd application > setup package. > My questions: > 1. > Why there is such difference between these 2 applications? > 2. > Should I include that excel.exe file with my distributable package or not. > (MS Office ver.10) > 3. > If yes to 2) above, do I need MSoft license to do that? > > Your comments appreciated, > Jack > Thank you all.
But still I do not know why Setup Wizard treats both my applications differently. Both have the same code: In Project>References I have selected: Microsoft Excel 10.0 Object library and then I just create (or set) Excel Object Set moExcelApp = GetObject(, "Excel.Application") If moExcelApp Is Nothing Then Set moExcelApp = CreateObject("Excel.Application") End If BTW, Is that considered early or late binding? I am not familiar with that term. Thanks, Jack Show quoteHide quote "Jack" <replyto@it> wrote in message news:u7MqZ0pWHHA.996@TK2MSFTNGP02.phx.gbl... > Hello, > I am confused by the Setup Wizard. > I have 2 applications which include Excel automation: (very simple > interaction with Excel spreadsheet, mostly just reading data from some > cells). > When preparing setup package for one application Setup Wizard does not > include excel.exe file, > but the same Setup Wizard includes excel.exe file with the 2nd application > setup package. > My questions: > 1. > Why there is such difference between these 2 applications? > 2. > Should I include that excel.exe file with my distributable package or not. > (MS Office ver.10) > 3. > If yes to 2) above, do I need MSoft license to do that? > > Your comments appreciated, > Jack >
Show quote
Hide quote
"Jack" <replyto@it> wrote in message Can't tell from that; how do you have moExcelApp declared?news:eMAfMGrWHHA.5068@TK2MSFTNGP03.phx.gbl > Thank you all. > But still I do not know why Setup Wizard treats both my applications > differently. > Both have the same code: > In Project>References I have selected: Microsoft Excel 10.0 Object > library and then I just create (or set) Excel Object > Set moExcelApp = GetObject(, "Excel.Application") > If moExcelApp Is Nothing Then > Set moExcelApp = CreateObject("Excel.Application") > End If > BTW, > Is that considered early or late binding? I am not > familiar with that term. Dim moExcelApp As Object ' late bound or Dim moExcelApp As Excel.Application ' early bound -- Reply to the group so all can participate VB.Net: "Fool me once..." I have:
Public WithEvents moExcelApp As Excel.Application Dim moExcelWBk As Excel.Workbook Dim moExcelWS As Excel.Worksheet So I believe it is an early bond. How that does influence the setup program? Please explain. Jack Show quoteHide quote "Bob Butler" <tiredofit@nospam.ever> wrote in message news:%23QOSJSrWHHA.600@TK2MSFTNGP05.phx.gbl... > "Jack" <replyto@it> wrote in message > news:eMAfMGrWHHA.5068@TK2MSFTNGP03.phx.gbl >> Thank you all. >> But still I do not know why Setup Wizard treats both my applications >> differently. >> Both have the same code: >> In Project>References I have selected: Microsoft Excel 10.0 Object >> library and then I just create (or set) Excel Object >> Set moExcelApp = GetObject(, "Excel.Application") >> If moExcelApp Is Nothing Then >> Set moExcelApp = CreateObject("Excel.Application") >> End If >> BTW, >> Is that considered early or late binding? I am not >> familiar with that term. > > Can't tell from that; how do you have moExcelApp declared? > Dim moExcelApp As Object ' late bound > or > Dim moExcelApp As Excel.Application ' early bound > > -- > Reply to the group so all can participate > VB.Net: "Fool me once..." > "Jack" <replyto@it> wrote in message It's early bound or an early binding; an early bond is when James arrivesnews:OhovtqsWHHA.1036@TK2MSFTNGP03.phx.gbl > I have: > Public WithEvents moExcelApp As Excel.Application > Dim moExcelWBk As Excel.Workbook > Dim moExcelWS As Excel.Worksheet > > So I believe it is an early bond. before he's expected <g> > How that does influence the setup program? Offhand, I can't based on what you've said. Are your references both to> Please explain. excel.exe or is one to the exe and one to a type library? You will find that the setup wizard does sometimes offer to include things you are using when you can't redistribute them. It's not a very robust application which is why many use other options (visual studio installer, inno setup, etc). -- Reply to the group so all can participate VB.Net: "Fool me once..." |
|||||||||||||||||||||||
Other interesting topics