Create a custom BO

You can use the current session to make connections to BOs either through the adapter approach or directly to the BO.

For example if you wanted to access the salesorder adapter from the BOL Entry screen.
Dim adSales As SalesOrderAdapter = New SalesOrderAdapter("BOLForm")
adSales.BOConnect()

Dim result As Boolean = adSales.BOConnect()
' do something with it

adSales.Dispose()

To work directly with the BO instead, similar to how things work via the BL Tester. You can use the Session property to get the needed information. Only have a C# example at the moment, there is a quirk/bug in 9 in that you can't get the reference to the session directly hence the extra step.

// need to cast the session property before using it
Epicor.Mfg.Core.Session s = (Epicor.Mfg.Core.Session)SalesOrderTrackerForm.Session;

SchedulingBoardBO = new Epicor.Mfg.BO.SchedulingBoard(s.ConnectionPool);

Jim Kinneman
Senior Consultant
Encompass Solutions, Inc

--- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@...> wrote:
>
> Hi ,
>
> What's the best way of using the current connection / getting the users session as I have only tried creating a new connection as follows:
>
> Private conepr As New Epicor.Mfg.Core.BLConnectionPool("account", "password", "AppServerDC://server:8331") 'Pilot
>
> Private objSO As New Epicor.Mfg.BO.SalesOrder(conepr)
>
> This works but uses up a licence and as you mentioned the ability to piggy-back on the current session this would be a better way of doing it. Have you got an example code snippet on how I can use the current user session. It would be appreciated.
>
> Thanks again.
>
> Cheers,
>
> Ross
>
>
> --- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@> wrote:
> >
> > Brian wrote:
> > > You could write an "extension" for Vantage that you could launch with
> > > a button click, that you could pass information to, which would launch a
> > > Vantage session, do stuff, and show the results in your custom
> > > extension. It wouldn't happen in the context of the users' session,
> > > which could lead to some license consumption issues, but only if you
> > > were getting close to using up your concurrent licenses anyways.
> >
> > Your custom code should be able to piggy-back on the current session
> > without starting a new one.
> >
> > With the current Load Library vulnerabilities that's causing many
> > updates these days makes me wonder if Epicor/Vantage are
> > susceptible...
> >
> > You would also want to do the custom client thingy to make sure that
> > the most up-date-date version of your dll was pushed out to the
> > clients...
> >
> > Mark W.
> >
>
Hi,

I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
Any help or ideas would be appreciated.

Regards

Ross
Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?

Jim Kinneman
Senior Consultant
Encompass Solutions, Inc

--- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@...> wrote:
>
> Hi,
>
> I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> Any help or ideas would be appreciated.
>
> Regards
>
> Ross
>
You don't write the *BO.dll it is generated by the custom proxygen part
of the SDK tools process within the object designer.

You create a .p file for your business object, define your public
procedures you require, then the proxy class is generated along with the
IF with the typed datasets.



Regards,

Stephen



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of ross_edinburgh
Sent: 02 September 2010 18:38
To: vantage@yahoogroups.com
Subject: [Vantage] Create a custom BO





Hi,

I was wondering if anyone has tried to create a custom BO. Using visual
studio I created a .dll file that I tried to reference via a custom
screen but it did not recognise it.
Any help or ideas would be appreciated.

Regards

Ross





[Non-text portions of this message have been removed]
Hi Jim,

We don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens. I have not tried adding an assembly reference. Can I do this using visual studio? Is this a file within the client directory?
When I try to add my .dll file it just does not recognise it and is not added. No errors are received.
My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system and to try and reduce the amount of duplicate code between screens. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.

Thanks

Ross



--- In vantage@yahoogroups.com, "jckinneman" <jckinneman@...> wrote:
>
> Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?
>
> Jim Kinneman
> Senior Consultant
> Encompass Solutions, Inc
>
> --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> >
> > Hi,
> >
> > I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> > Any help or ideas would be appreciated.
> >
> > Regards
> >
> > Ross
> >
>
Hi Stephen,

I just replied to Jim but we don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens.
I have access to visual studio. Is there any way that I can create code within here and compile into a .dll and reference it within screens that I have created? Or it this just not possible? In my visual studio I have an option to create a dynamic linked library project.
My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.

Thanks

Ross



--- In vantage@yahoogroups.com, "Stephen Edginton" <stephene@...> wrote:
>
> You don't write the *BO.dll it is generated by the custom proxygen part
> of the SDK tools process within the object designer.
>
> You create a .p file for your business object, define your public
> procedures you require, then the proxy class is generated along with the
> IF with the typed datasets.
>
>
>
> Regards,
>
> Stephen
>
>
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of ross_edinburgh
> Sent: 02 September 2010 18:38
> To: vantage@yahoogroups.com
> Subject: [Vantage] Create a custom BO
>
>
>
>
>
> Hi,
>
> I was wondering if anyone has tried to create a custom BO. Using visual
> studio I created a .dll file that I tried to reference via a custom
> screen but it did not recognise it.
> Any help or ideas would be appreciated.
>
> Regards
>
> Ross
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
If you create a DLL/Assembly using Visual Studio you can add it as an assembly reference the same way you would add a reference to an Epicor Adapter. And then add the appropriate using/imports statement in your custom code. At that point you should be able to treat it like any other assembly.

I have created new screens and functions/classes/objects this way without the SDK.

For example you might create a class that has methods for looking up information from an external SQL Server database. Instead of building the class within the embedded customization, you could put it into its own assembly and then can call it from many embedded customizations instead of duplicating the code in each.

BO in the context of Epicor does require the SDK so that all pieces of Epicor will see it such as BPMs and the like. But there is nothing stopping you from creating your own objects and the like that you call when you want to, understanding that the rest of Epicor will have no knowledge of them.

Jim Kinneman
Senior Consultant.
Encompass Solutions

--- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@...> wrote:
>
> Hi Jim,
>
> We don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens. I have not tried adding an assembly reference. Can I do this using visual studio? Is this a file within the client directory?
> When I try to add my .dll file it just does not recognise it and is not added. No errors are received.
> My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system and to try and reduce the amount of duplicate code between screens. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.
>
> Thanks
>
> Ross
>
>
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?
> >
> > Jim Kinneman
> > Senior Consultant
> > Encompass Solutions, Inc
> >
> > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > >
> > > Hi,
> > >
> > > I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> > > Any help or ideas would be appreciated.
> > >
> > > Regards
> > >
> > > Ross
> > >
> >
>
I forgot to talk about how to add the reference.

When you are in customization mode for a screen, go to the actions menu and pick add assembly reference. When it opens you will need to navigate to where you built your DLL if you did not put it into the Epicor client directory. Pick the file, OK/save your way out.

Then add the using/imports based on your language choice. C# is preferred for 9.

You can do this with just about any DLL, for example if you want to interact with Crystal Report objects you can include the DLLs for it. Then you can run and present a crystal report directly in an embedded customization.

Jim Kinneman

--- In vantage@yahoogroups.com, "jckinneman" <jckinneman@...> wrote:
>
> If you create a DLL/Assembly using Visual Studio you can add it as an assembly reference the same way you would add a reference to an Epicor Adapter. And then add the appropriate using/imports statement in your custom code. At that point you should be able to treat it like any other assembly.
>
> I have created new screens and functions/classes/objects this way without the SDK.
>
> For example you might create a class that has methods for looking up information from an external SQL Server database. Instead of building the class within the embedded customization, you could put it into its own assembly and then can call it from many embedded customizations instead of duplicating the code in each.
>
> BO in the context of Epicor does require the SDK so that all pieces of Epicor will see it such as BPMs and the like. But there is nothing stopping you from creating your own objects and the like that you call when you want to, understanding that the rest of Epicor will have no knowledge of them.
>
> Jim Kinneman
> Senior Consultant.
> Encompass Solutions
>
> --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> >
> > Hi Jim,
> >
> > We don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens. I have not tried adding an assembly reference. Can I do this using visual studio? Is this a file within the client directory?
> > When I try to add my .dll file it just does not recognise it and is not added. No errors are received.
> > My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system and to try and reduce the amount of duplicate code between screens. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.
> >
> > Thanks
> >
> > Ross
> >
> >
> >
> > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > >
> > > Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?
> > >
> > > Jim Kinneman
> > > Senior Consultant
> > > Encompass Solutions, Inc
> > >
> > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> > > > Any help or ideas would be appreciated.
> > > >
> > > > Regards
> > > >
> > > > Ross
> > > >
> > >
> >
>
Hi Jim,

I am still having a bit of bother we are on version 8.03.408B. I have gone into one of my custom screens and under tools assembly reference manager tried to add my custom .dll file.
I click on the file to select it but the details do not populate and the reference does not populate under any of the folders, system, native, custom assemblies. Do I need to add a reference to an epicor .dll within my visual studio project or do anything else to the build.
All the epicor .dll files reference without any issue. Is it worth me trying to reference a crystal .dll file or I don't know if you have a sample file that I could try and reference.

Thanks for your help.

Cheers,

Ross


--- In vantage@yahoogroups.com, "jckinneman" <jckinneman@...> wrote:
>
> I forgot to talk about how to add the reference.
>
> When you are in customization mode for a screen, go to the actions menu and pick add assembly reference. When it opens you will need to navigate to where you built your DLL if you did not put it into the Epicor client directory. Pick the file, OK/save your way out.
>
> Then add the using/imports based on your language choice. C# is preferred for 9.
>
> You can do this with just about any DLL, for example if you want to interact with Crystal Report objects you can include the DLLs for it. Then you can run and present a crystal report directly in an embedded customization.
>
> Jim Kinneman
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > If you create a DLL/Assembly using Visual Studio you can add it as an assembly reference the same way you would add a reference to an Epicor Adapter. And then add the appropriate using/imports statement in your custom code. At that point you should be able to treat it like any other assembly.
> >
> > I have created new screens and functions/classes/objects this way without the SDK.
> >
> > For example you might create a class that has methods for looking up information from an external SQL Server database. Instead of building the class within the embedded customization, you could put it into its own assembly and then can call it from many embedded customizations instead of duplicating the code in each.
> >
> > BO in the context of Epicor does require the SDK so that all pieces of Epicor will see it such as BPMs and the like. But there is nothing stopping you from creating your own objects and the like that you call when you want to, understanding that the rest of Epicor will have no knowledge of them.
> >
> > Jim Kinneman
> > Senior Consultant.
> > Encompass Solutions
> >
> > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > >
> > > Hi Jim,
> > >
> > > We don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens. I have not tried adding an assembly reference. Can I do this using visual studio? Is this a file within the client directory?
> > > When I try to add my .dll file it just does not recognise it and is not added. No errors are received.
> > > My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system and to try and reduce the amount of duplicate code between screens. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.
> > >
> > > Thanks
> > >
> > > Ross
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > > >
> > > > Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?
> > > >
> > > > Jim Kinneman
> > > > Senior Consultant
> > > > Encompass Solutions, Inc
> > > >
> > > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> > > > > Any help or ideas would be appreciated.
> > > > >
> > > > > Regards
> > > > >
> > > > > Ross
> > > > >
> > > >
> > >
> >
>
Hi Jim,

Thanks for your help. I managed to get the .dll to reference correctly in the end.

Cheers,

Ross

--- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@...> wrote:
>
> Hi Jim,
>
> I am still having a bit of bother we are on version 8.03.408B. I have gone into one of my custom screens and under tools assembly reference manager tried to add my custom .dll file.
> I click on the file to select it but the details do not populate and the reference does not populate under any of the folders, system, native, custom assemblies. Do I need to add a reference to an epicor .dll within my visual studio project or do anything else to the build.
> All the epicor .dll files reference without any issue. Is it worth me trying to reference a crystal .dll file or I don't know if you have a sample file that I could try and reference.
>
> Thanks for your help.
>
> Cheers,
>
> Ross
>
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > I forgot to talk about how to add the reference.
> >
> > When you are in customization mode for a screen, go to the actions menu and pick add assembly reference. When it opens you will need to navigate to where you built your DLL if you did not put it into the Epicor client directory. Pick the file, OK/save your way out.
> >
> > Then add the using/imports based on your language choice. C# is preferred for 9.
> >
> > You can do this with just about any DLL, for example if you want to interact with Crystal Report objects you can include the DLLs for it. Then you can run and present a crystal report directly in an embedded customization.
> >
> > Jim Kinneman
> >
> > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > >
> > > If you create a DLL/Assembly using Visual Studio you can add it as an assembly reference the same way you would add a reference to an Epicor Adapter. And then add the appropriate using/imports statement in your custom code. At that point you should be able to treat it like any other assembly.
> > >
> > > I have created new screens and functions/classes/objects this way without the SDK.
> > >
> > > For example you might create a class that has methods for looking up information from an external SQL Server database. Instead of building the class within the embedded customization, you could put it into its own assembly and then can call it from many embedded customizations instead of duplicating the code in each.
> > >
> > > BO in the context of Epicor does require the SDK so that all pieces of Epicor will see it such as BPMs and the like. But there is nothing stopping you from creating your own objects and the like that you call when you want to, understanding that the rest of Epicor will have no knowledge of them.
> > >
> > > Jim Kinneman
> > > Senior Consultant.
> > > Encompass Solutions
> > >
> > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > > >
> > > > Hi Jim,
> > > >
> > > > We don't have the SDK kit due to the cost of the software but we can write custom code for the vantage screens. I have not tried adding an assembly reference. Can I do this using visual studio? Is this a file within the client directory?
> > > > When I try to add my .dll file it just does not recognise it and is not added. No errors are received.
> > > > My plan was to start writing classes and store them within .dll files as we have been writing a lot of code for various screens / dashboards within the system and to try and reduce the amount of duplicate code between screens. My plan was then to try and set them up similar to .CSG modifications where these files would download to the client pc's.
> > > >
> > > > Thanks
> > > >
> > > > Ross
> > > >
> > > >
> > > >
> > > > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > > > >
> > > > > Did you add an assembly reference to your new dll? What kind of error indications are you getting when you do a Test Code or try to run it?
> > > > >
> > > > > Jim Kinneman
> > > > > Senior Consultant
> > > > > Encompass Solutions, Inc
> > > > >
> > > > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I was wondering if anyone has tried to create a custom BO. Using visual studio I created a .dll file that I tried to reference via a custom screen but it did not recognise it.
> > > > > > Any help or ideas would be appreciated.
> > > > > >
> > > > > > Regards
> > > > > >
> > > > > > Ross
> > > > > >
> > > > >
> > > >
> > >
> >
>
Jim, does this hard-code the DLL path into the assembly reference? Or
does the assembly just have to be somewhere in the assembly search path
(which I guess is basically the GAC or the client directory unless the
assembly is strongly-named)?

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of jckinneman
Sent: Thursday, September 02, 2010 5:47 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Create a custom BO

I forgot to talk about how to add the reference.

When you are in customization mode for a screen, go to the actions menu
and pick add assembly reference. When it opens you will need to
navigate to where you built your DLL if you did not put it into the
Epicor client directory. Pick the file, OK/save your way out.

Then add the using/imports based on your language choice. C# is
preferred for 9.

You can do this with just about any DLL, for example if you want to
interact with Crystal Report objects you can include the DLLs for it.
Then you can run and present a crystal report directly in an embedded
customization.

Jim Kinneman

--- In vantage@yahoogroups.com, "jckinneman" <jckinneman@...> wrote:
>
> If you create a DLL/Assembly using Visual Studio you can add it as an
assembly reference the same way you would add a reference to an Epicor
Adapter. And then add the appropriate using/imports statement in your
custom code. At that point you should be able to treat it like any
other assembly.
>
> I have created new screens and functions/classes/objects this way
without the SDK.
>
> For example you might create a class that has methods for looking up
information from an external SQL Server database. Instead of building
the class within the embedded customization, you could put it into its
own assembly and then can call it from many embedded customizations
instead of duplicating the code in each.
>
> BO in the context of Epicor does require the SDK so that all pieces of
Epicor will see it such as BPMs and the like. But there is nothing
stopping you from creating your own objects and the like that you call
when you want to, understanding that the rest of Epicor will have no
knowledge of them.
>
> Jim Kinneman
> Senior Consultant.
> Encompass Solutions
>
> --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@>
wrote:
> >
> > Hi Jim,
> >
> > We don't have the SDK kit due to the cost of the software but we can
write custom code for the vantage screens. I have not tried adding an
assembly reference. Can I do this using visual studio? Is this a file
within the client directory?
> > When I try to add my .dll file it just does not recognise it and is
not added. No errors are received.
> > My plan was to start writing classes and store them within .dll
files as we have been writing a lot of code for various screens /
dashboards within the system and to try and reduce the amount of
duplicate code between screens. My plan was then to try and set them up
similar to .CSG modifications where these files would download to the
client pc's.
> >
> > Thanks
> >
> > Ross
> >
> >
> >
> > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > >
> > > Did you add an assembly reference to your new dll? What kind of
error indications are you getting when you do a Test Code or try to run
it?
> > >
> > > Jim Kinneman
> > > Senior Consultant
> > > Encompass Solutions, Inc
> > >
> > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@>
wrote:
> > > >
> > > > Hi,
> > > >
> > > > I was wondering if anyone has tried to create a custom BO. Using
visual studio I created a .dll file that I tried to reference via a
custom screen but it did not recognise it.
> > > > Any help or ideas would be appreciated.
> > > >
> > > > Regards
> > > >
> > > > Ross
> > > >
> > >
> >
>




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Folks here have written code that talks to the client BOs directly in
.NET.

You could write an "extension" for Vantage that you could launch with
a button click, that you could pass information to, which would launch a
Vantage session, do stuff, and show the results in your custom
extension. It wouldn't happen in the context of the users' session,
which could lead to some license consumption issues, but only if you
were getting close to using up your concurrent licenses anyways.

-bws

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of jckinneman
Sent: Thursday, September 02, 2010 5:36 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Create a custom BO

If you create a DLL/Assembly using Visual Studio you can add it as an
assembly reference the same way you would add a reference to an Epicor
Adapter. And then add the appropriate using/imports statement in your
custom code. At that point you should be able to treat it like any
other assembly.

I have created new screens and functions/classes/objects this way
without the SDK.

For example you might create a class that has methods for looking up
information from an external SQL Server database. Instead of building
the class within the embedded customization, you could put it into its
own assembly and then can call it from many embedded customizations
instead of duplicating the code in each.

BO in the context of Epicor does require the SDK so that all pieces of
Epicor will see it such as BPMs and the like. But there is nothing
stopping you from creating your own objects and the like that you call
when you want to, understanding that the rest of Epicor will have no
knowledge of them.

Jim Kinneman
Senior Consultant.
Encompass Solutions

--- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@...>
wrote:
>
> Hi Jim,
>
> We don't have the SDK kit due to the cost of the software but we can
write custom code for the vantage screens. I have not tried adding an
assembly reference. Can I do this using visual studio? Is this a file
within the client directory?
> When I try to add my .dll file it just does not recognise it and is
not added. No errors are received.
> My plan was to start writing classes and store them within .dll files
as we have been writing a lot of code for various screens / dashboards
within the system and to try and reduce the amount of duplicate code
between screens. My plan was then to try and set them up similar to .CSG
modifications where these files would download to the client pc's.
>
> Thanks
>
> Ross
>
>
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > Did you add an assembly reference to your new dll? What kind of
error indications are you getting when you do a Test Code or try to run
it?
> >
> > Jim Kinneman
> > Senior Consultant
> > Encompass Solutions, Inc
> >
> > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@>
wrote:
> > >
> > > Hi,
> > >
> > > I was wondering if anyone has tried to create a custom BO. Using
visual studio I created a .dll file that I tried to reference via a
custom screen but it did not recognise it.
> > > Any help or ideas would be appreciated.
> > >
> > > Regards
> > >
> > > Ross
> > >
> >
>




------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
Brian wrote:
> You could write an "extension" for Vantage that you could launch with
> a button click, that you could pass information to, which would launch a
> Vantage session, do stuff, and show the results in your custom
> extension. It wouldn't happen in the context of the users' session,
> which could lead to some license consumption issues, but only if you
> were getting close to using up your concurrent licenses anyways.

Your custom code should be able to piggy-back on the current session
without starting a new one.

With the current Load Library vulnerabilities that's causing many
updates these days makes me wonder if Epicor/Vantage are
susceptible...

You would also want to do the custom client thingy to make sure that
the most up-date-date version of your dll was pushed out to the
clients...

Mark W.
I usually put the DLL in the Epicor client directory so haven't had to verify where it looks for the DLL, someone with more experience may be able to chime in with more details. The DLL will need to be available on the system(s) that users run Epicor on. That is one reason I default to the client directory as it simplifies deployment.

Jim K.

--- In vantage@yahoogroups.com, "Brian W. Spolarich " <bspolarich@...> wrote:
>
> Jim, does this hard-code the DLL path into the assembly reference? Or
> does the assembly just have to be somewhere in the assembly search path
> (which I guess is basically the GAC or the client directory unless the
> assembly is strongly-named)?
>
> -bws
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of jckinneman
> Sent: Thursday, September 02, 2010 5:47 PM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Create a custom BO
>
> I forgot to talk about how to add the reference.
>
> When you are in customization mode for a screen, go to the actions menu
> and pick add assembly reference. When it opens you will need to
> navigate to where you built your DLL if you did not put it into the
> Epicor client directory. Pick the file, OK/save your way out.
>
> Then add the using/imports based on your language choice. C# is
> preferred for 9.
>
> You can do this with just about any DLL, for example if you want to
> interact with Crystal Report objects you can include the DLLs for it.
> Then you can run and present a crystal report directly in an embedded
> customization.
>
> Jim Kinneman
>
> --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> >
> > If you create a DLL/Assembly using Visual Studio you can add it as an
> assembly reference the same way you would add a reference to an Epicor
> Adapter. And then add the appropriate using/imports statement in your
> custom code. At that point you should be able to treat it like any
> other assembly.
> >
> > I have created new screens and functions/classes/objects this way
> without the SDK.
> >
> > For example you might create a class that has methods for looking up
> information from an external SQL Server database. Instead of building
> the class within the embedded customization, you could put it into its
> own assembly and then can call it from many embedded customizations
> instead of duplicating the code in each.
> >
> > BO in the context of Epicor does require the SDK so that all pieces of
> Epicor will see it such as BPMs and the like. But there is nothing
> stopping you from creating your own objects and the like that you call
> when you want to, understanding that the rest of Epicor will have no
> knowledge of them.
> >
> > Jim Kinneman
> > Senior Consultant.
> > Encompass Solutions
> >
> > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@>
> wrote:
> > >
> > > Hi Jim,
> > >
> > > We don't have the SDK kit due to the cost of the software but we can
> write custom code for the vantage screens. I have not tried adding an
> assembly reference. Can I do this using visual studio? Is this a file
> within the client directory?
> > > When I try to add my .dll file it just does not recognise it and is
> not added. No errors are received.
> > > My plan was to start writing classes and store them within .dll
> files as we have been writing a lot of code for various screens /
> dashboards within the system and to try and reduce the amount of
> duplicate code between screens. My plan was then to try and set them up
> similar to .CSG modifications where these files would download to the
> client pc's.
> > >
> > > Thanks
> > >
> > > Ross
> > >
> > >
> > >
> > > --- In vantage@yahoogroups.com, "jckinneman" <jckinneman@> wrote:
> > > >
> > > > Did you add an assembly reference to your new dll? What kind of
> error indications are you getting when you do a Test Code or try to run
> it?
> > > >
> > > > Jim Kinneman
> > > > Senior Consultant
> > > > Encompass Solutions, Inc
> > > >
> > > > --- In vantage@yahoogroups.com, "ross_edinburgh" <ross_edinburgh@>
> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I was wondering if anyone has tried to create a custom BO. Using
> visual studio I created a .dll file that I tried to reference via a
> custom screen but it did not recognise it.
> > > > > Any help or ideas would be appreciated.
> > > > >
> > > > > Regards
> > > > >
> > > > > Ross
> > > > >
> > > >
> > >
> >
>
>
>
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
Hi ,

What's the best way of using the current connection / getting the users session as I have only tried creating a new connection as follows:

Private conepr As New Epicor.Mfg.Core.BLConnectionPool("account", "password", "AppServerDC://server:8331") 'Pilot

Private objSO As New Epicor.Mfg.BO.SalesOrder(conepr)

This works but uses up a licence and as you mentioned the ability to piggy-back on the current session this would be a better way of doing it. Have you got an example code snippet on how I can use the current user session. It would be appreciated.

Thanks again.

Cheers,

Ross


--- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@...> wrote:
>
> Brian wrote:
> > You could write an "extension" for Vantage that you could launch with
> > a button click, that you could pass information to, which would launch a
> > Vantage session, do stuff, and show the results in your custom
> > extension. It wouldn't happen in the context of the users' session,
> > which could lead to some license consumption issues, but only if you
> > were getting close to using up your concurrent licenses anyways.
>
> Your custom code should be able to piggy-back on the current session
> without starting a new one.
>
> With the current Load Library vulnerabilities that's causing many
> updates these days makes me wonder if Epicor/Vantage are
> susceptible...
>
> You would also want to do the custom client thingy to make sure that
> the most up-date-date version of your dll was pushed out to the
> clients...
>
> Mark W.
>