I have five different ASP.NET Web Applications. I started one project, downloaded the AJAX Toolkit using Nuget, which installs packages per project. The controls tab was not added to the toolbox. So I added them manually. No problem.
For each subsequent project I've created, I've installed a Nuget package for the ASP.NET Web application.
But I have to re-set the toolbox for each project, because each project has a different package in a different location.
There seem to be no clear instructions. Where's the ease of using NuGet if I have to reset the toolbox for every solution I work on?
If I set the toolbox for Project A, based on the NuGet package for Project A.
Then when I save, and close Project A, and open up Project B, the AJAX Toolkit items in the toolbox, refer to the package for Project A. Instead of referencing the package for Project B.
I could include a screenshot, but this can be easily demonstrated in the following steps.
Pre-Req (Do not have AJAX Toolkit installed, only using NuGet to manage packages)
1. Create Web Application (VS 2012)
2. Install NuGet package for AJAX Toolkit (3.5)
3. Manually set the toolbox by browsing to the AJAX Toolkit DLL that was installed in step 2.
4. Add AJAX control to page on project (including toolkitscriptmanager)
5. Save and close
6. Create new Web Application (VS 2012)
7. Use NuGet package installer for AJAX Toolkit (3.5)
8. Existing Toolkit tab should still exist.
9. Right-click tab, Choose Toolbox Items
10. Find an existing toolbox item, such as Accordian.
11. Expand "Directory" column, Path to AJAXToolkit.dll is the location of the NuGet package from first project created in Step 1.
12. Re-setting the toolbox clear that out
13. Manually adding the toolbox for the most recent Project
14. Develop, Test, Close, Save.
15. Go back to first project
16. No errors if you are using the same version of the package.
17. Lots of errors if the package version is different.
* The difference in packages was because I created one web application during 2011, the second package was created in late 2012.
Everytime I switch back and forth between the two applications, do I have to reset the toolbox?
Everytime I start a new project, do I have to update all the other projects, so I have only one version of the AJAX toolkit?
** Some clarification is needed to understand how to EFFECTIVELY use NuGet packages to manage the use of the AJAX Toolkit in solutions.
** Why has no one even looked at this issue? If there is some magic way of handling this issue, then can someone take the time to at least post how they get around this problem?
Comments: This is by design. NuGet packages operate only at the project or solution level. They cannot affect Visual Studio's toolbox since it is a part of the Visual Studio environment shared across multiple projects/solutions. With the latest v15.1 version of ASP.NET AJAX Control Toolkit, it is possible to use the installer, which will automatically populate a Visual Studio toolbox and place appropriate .dll to the shared location.
For each subsequent project I've created, I've installed a Nuget package for the ASP.NET Web application.
But I have to re-set the toolbox for each project, because each project has a different package in a different location.
There seem to be no clear instructions. Where's the ease of using NuGet if I have to reset the toolbox for every solution I work on?
If I set the toolbox for Project A, based on the NuGet package for Project A.
Then when I save, and close Project A, and open up Project B, the AJAX Toolkit items in the toolbox, refer to the package for Project A. Instead of referencing the package for Project B.
I could include a screenshot, but this can be easily demonstrated in the following steps.
Pre-Req (Do not have AJAX Toolkit installed, only using NuGet to manage packages)
1. Create Web Application (VS 2012)
2. Install NuGet package for AJAX Toolkit (3.5)
3. Manually set the toolbox by browsing to the AJAX Toolkit DLL that was installed in step 2.
4. Add AJAX control to page on project (including toolkitscriptmanager)
5. Save and close
6. Create new Web Application (VS 2012)
7. Use NuGet package installer for AJAX Toolkit (3.5)
8. Existing Toolkit tab should still exist.
9. Right-click tab, Choose Toolbox Items
10. Find an existing toolbox item, such as Accordian.
11. Expand "Directory" column, Path to AJAXToolkit.dll is the location of the NuGet package from first project created in Step 1.
12. Re-setting the toolbox clear that out
13. Manually adding the toolbox for the most recent Project
14. Develop, Test, Close, Save.
15. Go back to first project
16. No errors if you are using the same version of the package.
17. Lots of errors if the package version is different.
* The difference in packages was because I created one web application during 2011, the second package was created in late 2012.
Everytime I switch back and forth between the two applications, do I have to reset the toolbox?
Everytime I start a new project, do I have to update all the other projects, so I have only one version of the AJAX toolkit?
** Some clarification is needed to understand how to EFFECTIVELY use NuGet packages to manage the use of the AJAX Toolkit in solutions.
** Why has no one even looked at this issue? If there is some magic way of handling this issue, then can someone take the time to at least post how they get around this problem?
Comments: This is by design. NuGet packages operate only at the project or solution level. They cannot affect Visual Studio's toolbox since it is a part of the Visual Studio environment shared across multiple projects/solutions. With the latest v15.1 version of ASP.NET AJAX Control Toolkit, it is possible to use the installer, which will automatically populate a Visual Studio toolbox and place appropriate .dll to the shared location.