none
Has anyone successfully installed Management Portal for BizTalk 2013 ESB Toolkit? RRS feed

  • Question

  • The fact that Microsoft left the ESB Toolkit Management Portal as a sample is baffling to say the least. What is really frustrating is that installation of this portal seems to have become more cumbersome than it used to be before.

    After unpacking the ESBSource.zip as it is suggested in the documentation (for ESB 2.1, there is nothing on this subject for the current version) into the C:\Projects\Microsoft.Practices.ESB folder and trying to run Management_Install.cmd from C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts, I am getting all sorts of warnings and errors:

    warning MSB3245: Could not resolve this reference. Could not locate the assembly "ESB.BAM.Service.Implementation". Check to make sure the assembly exists on disk. 
    warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.ReportViewer.Common, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". 
    warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". 
    Faults\Itineraries.aspx.cs(8,11): error CS0234: The type or namespace name 'BAM' does not exist in the namespace 'ESB' (are you missing an assembly reference?) [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\ESB.Portal.csproj]
    Faults\MessageViewer.ascx.cs(41,11): error CS0234: The type or namespace name 'BAM' does not exist in the namespace 'ESB' (are you missing an assembly reference?) [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\ESB.Portal.csproj]
    DAL\DALHelper.cs(21,13): error CS0012: The type 'Microsoft.Practices.ServiceLocation.IServiceLocator' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Practices.ServiceLocation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. [C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.BAM.Service\ESB.BAM.Service\ESB.BAM.Service.Implementation\ESB.BAM.Service.Implementation.csproj]

    The installation proceeds, but the portal of course is not functional in the end since the build fails.

    A quick look at the solutions and projects under the Samples\Management Portal folder reveals that all the service solutions (Alert Service, BAM Service, Exception Service, UDDIS Publisher Service) are Visual Studio 2012 solutions and their corresponding setup projects are WiX projects. Though, the ESB.Portal.sln is actually Visual Studio 2010 solution that still contains a Visual Studio Setup project (not available in Visual Studio 2012).

    Now, I would really like to hear any suggestions from Microsoft team on how we are supposed to install the ESB Toolkit Management Portal. Even just telling us what the real pre-requisites for this installation are would be very helpful, since relying on the ESB 2.1 installation guide does not seem to be working anymore.

    Microsoft team: your help would be greatly appreciated.

    Thank you,

    --Vlad



    Vladimir Kirnishni



    Tuesday, March 26, 2013 8:03 PM

Answers

  • Here are the steps to install the Management Portal for ESB Toolkit 2.2 that ships with BizTalk 2013. After the ESB Toolkit has been installed and configured:

    1. Unzip C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\ESBSource.zip file into the C:\Projects\Microsoft.Practices.ESB folder
    2. Remove Read-only attribute from all files in C:\Projects\Microsoft.Practices.ESB folder.
    3. Download and install Enterprise Library 5.0 from http://www.microsoft.com/en-us/download/details.aspx?id=15104
    4. Download and install Microsoft Report Viewer Redistributable 2008  from http://www.microsoft.com/en-us/download/details.aspx?id=577
    5. In Visual Studio 2012, open ESB.Portal.sln found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
    6. When Visual Studio 2012 starts converting the solution to the current format, a dialog pops up that warns you about ESB.Portal.Setup.vdproj file not being supported in Visual Studio 2012. Click OK. Wait until the solution opens.
    7. In the Solution Explorer add Microsoft.Practices.ServiceLocation.dll as a reference to the ESB.BAM.Service.Implementation project. This assembly is found in C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
    8. Open web.config file found in ESB.Portal project and remove (or comment out) "scripting" sectionGroup declaration that starts at line 12 and ends at line 20.
    9. Save all files in the solution.
    10. Rebuild ESB.Portal solution.
    11. Close Visual Studio.
    12. Run Management_Install.cmd file found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts

    Now when you open Internet Explorer and navigate to http://localhost/ESB.Portal you should see the ESB Management Console home page.

    Regards,

    --Vlad


    Vladimir Kirnishni



    • Edited by Vladimir Kirnishni Tuesday, April 2, 2013 5:31 PM Added solution rebuild step (10), edited step 8 to remove the whole "scripting" section
    • Proposed as answer by mdiiorio Wednesday, April 3, 2013 9:30 PM
    • Marked as answer by Ben Cline1Moderator Thursday, April 4, 2013 6:11 PM
    Thursday, March 28, 2013 7:42 PM

All replies

  • Here is a little bit more information on the ESB Toolkit 2.2 Management Portal that ships with BizTalk 2013.

    When one tries to open the ESB.Portal.sln (found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal) in Visual Studio, it fails.

    It is not possible to open this solution in Visual Studio 2012 or Visual Studio 2010!

    In ESB 2.1 that was available in BizTalk 2010, you could just open this solution in Visual Studio 2010 and build.

    Now if you try to open the solution in Visual Studio 2010, the solution opens, but none of the projects open. All of them are displayed in Solution Explorer as incompatible with the current version of Visual Studio. When you try to open this solution in Visual Studio 2012, Visual Studio tries to convert the solution since the .sln file is actually in Visual Studio 2010 format, but cannot proceed normally since the solution contains the .vdproj file which is not supported in Visual Studio 2012. If you ignore this .vdproj file, the Visual Studio converts the solution to new format, but you cannot compile it. The build fails.

    This looks like a total mess!

    Regards,

    --Vlad


    Vladimir Kirnishni

    Wednesday, March 27, 2013 9:27 PM
  • Hi,

    You would expect this only in the Beta version but I see it indeed in the BizTalk Server 2013 Enterprise Edition that is available on MSDN Supscriptions,.

    Greetings,

    Tomasso Groenendijk

    Thursday, March 28, 2013 12:15 PM
  • Here are the steps to install the Management Portal for ESB Toolkit 2.2 that ships with BizTalk 2013. After the ESB Toolkit has been installed and configured:

    1. Unzip C:\Program Files (x86)\Microsoft BizTalk ESB Toolkit\ESBSource.zip file into the C:\Projects\Microsoft.Practices.ESB folder
    2. Remove Read-only attribute from all files in C:\Projects\Microsoft.Practices.ESB folder.
    3. Download and install Enterprise Library 5.0 from http://www.microsoft.com/en-us/download/details.aspx?id=15104
    4. Download and install Microsoft Report Viewer Redistributable 2008  from http://www.microsoft.com/en-us/download/details.aspx?id=577
    5. In Visual Studio 2012, open ESB.Portal.sln found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal
    6. When Visual Studio 2012 starts converting the solution to the current format, a dialog pops up that warns you about ESB.Portal.Setup.vdproj file not being supported in Visual Studio 2012. Click OK. Wait until the solution opens.
    7. In the Solution Explorer add Microsoft.Practices.ServiceLocation.dll as a reference to the ESB.BAM.Service.Implementation project. This assembly is found in C:\Program Files (x86)\Microsoft Enterprise Library 5.0\Bin
    8. Open web.config file found in ESB.Portal project and remove (or comment out) "scripting" sectionGroup declaration that starts at line 12 and ends at line 20.
    9. Save all files in the solution.
    10. Rebuild ESB.Portal solution.
    11. Close Visual Studio.
    12. Run Management_Install.cmd file found in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\Install\Scripts

    Now when you open Internet Explorer and navigate to http://localhost/ESB.Portal you should see the ESB Management Console home page.

    Regards,

    --Vlad


    Vladimir Kirnishni



    • Edited by Vladimir Kirnishni Tuesday, April 2, 2013 5:31 PM Added solution rebuild step (10), edited step 8 to remove the whole "scripting" section
    • Proposed as answer by mdiiorio Wednesday, April 3, 2013 9:30 PM
    • Marked as answer by Ben Cline1Moderator Thursday, April 4, 2013 6:11 PM
    Thursday, March 28, 2013 7:42 PM
  • Yeah... that didnt work...

    1. There is no  "webServices" in the web.config file found in ESB.Portal project

    2. When running the  Management_Install.cmd  from powershell (x86)... it throws 56 errors


    JAW

    Friday, March 29, 2013 3:59 PM
  • Vlad,

    I will report this to Microsoft support too. Thanks for pointing this out.

    I also tried to find documentation for the ESB management portal setup for 2013 but could not find any. I also asked for better documentation for this.

    Thanks,

    Ben


    If this answers your question, please use the "Answer" button to say so | Ben Cline


    Friday, March 29, 2013 6:37 PM
    Moderator
  • Hi Jim,

    I just went through configuring BizTalk 2013 and ESB Toolkit 2.2 on another clean VM image and I can confirm that all the steps that I mentioned before are required and they work with a little correction. After step 9, before closing Visual Studio re-build the solution first. Then the Management_Install.cmd should run without errors.

    The web.config file (in C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal) does contain "webServices" sectionGroup declaration. It starts at line 14. If you do not remove it, you will get a runtime error when opening the portal page in the browser. Actually, you need to remove (or comment out)  the whole parent "scripting" sectionGroup declaration as shown below:

    <!--
    <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
    				<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
    				<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
    					<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere"/>
    					<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
    					<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
    					<section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
    				</sectionGroup>
    </sectionGroup>
    -->

    Regards,

    --Vlad


    Vladimir Kirnishni


    Tuesday, April 2, 2013 5:15 PM
  • Nice work, Vlad.  I can confirm the installation steps work on a clean Windows Server 2012 x64 image.
    Wednesday, April 3, 2013 9:33 PM
  • There are a number of other issues if you  install on Windows 2012 with SharePoint 2013. I had to do a few addition reconfigurations in IIS to get the ESB Management Portal to work.

    Also the Web Reference for the UDDIService in the ESB.Portal has an incorrect URL.

    You need to modify the existing URL 

    http://localhost/ESB.UDDIService/UDDIService.asmx

    to

    http://localhost/ESB.UDDI.Service/UDDIService.asmx

    otherwise, the Registry -> New Registry Entry menu item will not work.



    • Edited by BusRider Tuesday, April 30, 2013 2:57 PM
    Tuesday, April 30, 2013 2:56 PM
  • Excellent. It works.

    Thanks...

    Thursday, June 27, 2013 4:02 AM
  • It would work without even installing Report Viewer Redistributable 2008 (version 9.0.0.0). With VS 2012 comes an upgraded version which is 11.0.0.0. You just need to update the assembly references to this version and also the public key. it works.

    • Proposed as answer by Ryan Gr Thursday, January 23, 2014 7:23 PM
    Thursday, June 27, 2013 4:09 AM
  • To configure ESB management portal ,i have followed Vlad suggestions  (In above ) ,but while running Management_Install.cmd (Tried dubble click the batch file and run from the command prompt)

    I am getting below error.

    Error: The term \Management_Install.ps1 is not recognized as the name of a cmdlet function script file or operable program.check the spelling of the name ,or if a path was included ,verify that the path is correc and try again .

    Any suggestion...

    Thursday, January 2, 2014 6:39 AM
  • "The fact that Microsoft left the ESB Toolkit Management Portal as a sample is baffling to say the least. What is really frustrating is that installation of this portal seems to have become more cumbersome than it used to be before."

    The ESB Management Portal is found in the Samples directory:

    According to the BizTalk Program Manager at Microsoft; Microsoft always has provided the portal as a sample of what could be done to enable management of the ESB Toolkit. It is far from being complete. They expected their partner community to take the foundational components of BizTalk and ESB and develop the house on top of it.

    Stott Creations has done that in a product called ESB Vision, which has the following components:

    • SharePoint Farm Solution that installs in minutes instead of hours/days, and integrates with AD
    • Ties faults to itineraries
    • Shows all steps in itinerary
    • Logs custom data along the itinerary's trip

    If you would like to see a demonstration of this let me know (eric@stottcreations.com).


    Eric Stott [http://biztalk.stottcreations.com] - Mark as Answer if this reply does.


    • Edited by Eric Stott Thursday, January 2, 2014 7:27 PM
    Thursday, January 2, 2014 7:25 PM
  • The problem here for us is that, having forked out all that money on licences, our BizTalk customers are generally not open to paying us lots of money to develop additional tooling.   It's a pity.   Providing the portal as a managed and maintained tool rather than sample code would be a fairly simple and cheap way to enhance the product.

    The portal, once you've got it working, is not brilliant, but does play to some of the strengths of the ESB toolkit - the error handling framework and ability to easily register BizTalk endpoints in the service directory.  On one current project we plan to use it as-is for these two purposes in conjunction with our own venerable pre-toolkit policy resolution framework.  Our framework is more powerful and more technology-agnostic than the resolution framework provided by the ESB toolkit.  We have no need for itineraries on that project.

    Getting the portal sample installed and configured is hard but not impossible.  We used the 'VDProj to WiX converter' tool from Add-In Express to migrate from the now-defunct installer project type to WiX.   See http://www.add-in-express.com/vdproj-wix-converter/index.php.   Our 2013 version of the portal uses the current version of Microsoft.ReportViewer.WebForms (version 11).


    Charles Young

    Thursday, January 9, 2014 11:55 PM
  • Vlad, thanks for the help...AWESOME. I found that before running the steps some basic prelims also need to be followed such as PS set execution policy to unrestricted, having installed UDDI and running publisher.exe etc.

    Hope this helps

    Thursday, January 23, 2014 7:23 PM
  • you can also simply drag over a chart control from the toolbox and then replace dundis charts with VS ones.... happy coding...
    Thursday, January 23, 2014 7:24 PM
  • I have received the below message when i am following steps to configure ESB Portal.

    I am trying to Rebuild ESB.Portal solution and it throws the below error

    Error 1 Warning as Error: Reference to type 'Microsoft.Practices.EnterpriseLibrary.Common.Configuration.IConfigurationSourceBuilder' claims it is defined in 'c:\Windows\assembly\GAC_MSIL\Microsoft.Practices.EnterpriseLibrary.Common\4.1.0.0__31bf3856ad364e35\Microsoft.Practices.EnterpriseLibrary.Common.dll', but it could not be found

    Error 2 The base class or interface of 'Microsoft.Practices.EnterpriseLibrary.Data.DatabaseProviderFactory' could not be resolved or is invalid

    Error 3 Warning as Error: Reference to type 'Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ContainerModel.ContainerBasedInstanceFactory`1' claims it is defined in 'c:\Windows\assembly\GAC_MSIL\Microsoft.Practices.EnterpriseLibrary.Common\4.1.0.0__31bf3856ad364e35\Microsoft.Practices.EnterpriseLibrary.Common.dll', but it could not be found

    Error 4 Assembly 'Microsoft.Practices.EnterpriseLibrary.Data, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' uses 'Microsoft.Practices.EnterpriseLibrary.Common, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' which has a higher version than referenced assembly 'Microsoft.Practices.EnterpriseLibrary.Common, Version=4.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'

    Error 5 'Microsoft.Practices.EnterpriseLibrary.Data.DatabaseProviderFactory' does not contain a definition for 'CreateDefault' and no extension method 'CreateDefault' accepting a first argument of type 'Microsoft.Practices.EnterpriseLibrary.Data.DatabaseProviderFactory' could be found (are you missing a using directive or an assembly reference?)

    Error 6 Metadata file 'C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.BAM.Service\ESB.BAM.Service\ESB.BAM.Service.Implementation\bin\Debug\ESB.BAM.Service.Implementation.dll' could not be found ESB.BAM.Service (Services\ESB.BAM.Service\ESB.BAM.Service)

    Any help is appreciated.

    Sunday, February 16, 2014 7:14 PM
  • Hi All,

    I followed the steps  given by Vladimir to install ESB Portal but while building the ESB.Portal solution I am facing following errors.

    Can someone point me to the right direction?

    1>------ Build started: Project: ESB.Portal, Configuration: Debug Any CPU ------

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\DataSets\Alerts.cs(1,47,1,66): error CS0234: The type or namespace name 'AlertsTableAdapters' does not exist in the namespace 'Microsoft.Practices.ESB.Portal.DataSets' (are you missing an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Alerts\AlertEdit.aspx.cs(29,25,29,33): error CS0426: The type name 'AlertRow' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Alerts\AlertEdit.aspx.cs(30,25,30,48): error CS0426: The type name 'AlertConditionDataTable' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Code\EmailHelper.cs(63,66,63,75): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Code\EmailHelper.cs(83,77,83,86): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\DataSets\Alerts.cs(104,16,104,39): error CS0246: The type or namespace name 'AlertConditionDataTable' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\DataSets\Alerts.cs(204,18,204,26): error CS0246: The type or namespace name 'AlertRow' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Lists\AlertList.ascx.cs(37,33,37,47): error CS0426: The type name 'AlertDataTable' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Lists\AlertList.ascx.cs(38,33,38,59): error CS0426: The type name 'AlertSubscriptionDataTable' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Lists\AlertList.ascx.cs(126,50,126,58): error CS0426: The type name 'AlertRow' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Lists\ConditionList.ascx.cs(35,33,35,56): error CS0426: The type name 'AlertConditionDataTable' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Lists\ConditionList.ascx.cs(37,32,37,55): error CS0426: The type name 'AlertConditionDataTable' does not exist in the type 'Microsoft.Practices.ESB.Portal.DataSets.Alerts'

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\AdminDatabaseService.cs(36,16,36,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\AdminDatabaseService.cs(56,16,56,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\AdminDatabaseService.cs(88,16,88,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\AdminDatabaseService.cs(141,39,141,48): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(44,16,44,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(67,16,67,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(86,40,86,49): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(107,45,107,54): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(158,50,158,59): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(167,48,167,57): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(178,17,178,26): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\ServiceProxy.cs(453,17,453,26): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\UDDIDetails.aspx.cs(39,17,39,26): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\UDDIDetails.aspx.cs(101,19,101,28): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\UDDIDetails.aspx.cs(114,16,114,25): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    1>C:\Projects\Microsoft.Practices.ESB\Source\Samples\Management Portal\ESB.Portal\Uddi\UDDIDetails.aspx.cs(188,37,188,46): error CS0246: The type or namespace name 'Endpoints' could not be found (are you missing a using directive or an assembly reference?)

    ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

    Saturday, March 15, 2014 4:49 AM
  • This was very helpful.  I have been working through a lot of frustration with ESB 2.3 and BizTalk 2013 R2 on many of the sample applications.  I found they make a lot of assumptions about where you have installed Visual Studio which in my case aren't exactly true because of drive space considerations.  Thank you.
    Monday, December 1, 2014 9:53 PM
  • Hi Vittalaranga,

    How did you resolve this powershell scripting error, I am facing the exactly same issue.

    Guys, anyone can point  if I need to tweak the cmd file to make it run??

    Regards,

    vikingsss

    Friday, February 6, 2015 4:56 AM