and a couple other things I seem to recall....
Make sure all objects created in the customization are disposed of properly and check to see if that is a cached form (for speed launching) - I have seen issues with customizations and cached forms....
Make sure all objects created in the customization are disposed of properly and check to see if that is a cached form (for speed launching) - I have seen issues with customizations and cached forms....
--- In vantage@yahoogroups.com, "cooner_55421" <cooner_55421@...> wrote:
>
> Thanks for all the info.
> I'm especially interested in trying Visual Studio now.
>
> BTW... I have an intermittent error I've been struggling with.
> I'm looking for ideas.
>
> This never occurs while in customization.
> It does not occur immediately after the customization has been deployed either.
>
> But once the deployed version fails, it will then fail pretty consistently.
> All I have to do to clear the error is open it in customization mode and exit.
>
> I'm sure something is being "set" and not clearing.
> But I've no idea what it could be & I'm not sure how I might catch it.
>
> Thanks again
>
> --- In vantage@yahoogroups.com, "Anton" <anton.ochss@> wrote:
> >
> > We have been using Visual Studio to debug. It works pretty well and also allows you do look deeper into the objects as well as set breakpoints and watches.
> >
> >
> > From the 9.05.604 Feature Summary Document
> >
> > Debugging Customizations in Visual Studio
> > If you have Microsoft Visual Studio, you can debug customizations and step through code Microsoft Visual Studio 2010 any version except Express must be installed on the computer where you are running the Epicor client. You should have C# or VB.NET (or both) installed in Visual Studio for complete debugging functionality.
> >
> > To debug a customization:
> >
> > 1. On a computer where Visual Studio is installed, start Epicor.
> > 2. From the Options menu, select Developer Mode.
> > 3. Navigate to the program you have customized. Double-click its icon.The Select Customizationwindow displays.
> > 4. In the Select Customization window, select the Debug in Visual Studio check box, click the customization layer you want to debug, and click OK
> >
> > .Visual Studio is launched into a source code file and stopped at a break point on the first line of theInitialize GlobalVariables method (this may take some time). At this point you can use the debugging features of Visual Studio to step though lines, set other break points, evaluate values etc. To get past the first breakpoint that was set for you and to run the form, press F5. Now if you complete actions on the form that reach a break point that you set, Visual Studio again becomes the active application (you may have to click its flashing item on the taskbar).
> >
> > Remember the following:
> > •You cannot make code changes in the debugger. Stop the debugger (Shift + F5), and use the Epicor customization environment to make your code changes. Then debug again as needed.
> > •Each time you debug a new source code file is opened in Visual Studio. Closing no longer active code files is ok. However, if you close Visual Studio, you have to exit Epicor and restart Epicor to debug again.
> >
> >
> >
> > --- In vantage@yahoogroups.com, Mark Wonsil <mark_wonsil@> wrote:
> > >
> > > > I'm wondering how you troubleshooting your customizations.
> > > > Any tips you can share?
> > >
> > > The word in .605 from the Epicor Users Group list is that you can
> > > debug with Visual Studio (not Express edition though).
> > >
> > > Mark W.
> > >
> >
>