What is an "AddOn" project? - acumatica

I have an Acumatica instruction document that seems to be from a much older version of Acumatica. In the documentation, it mentions that I need to go to System -> Customization -> Manage -> Customization Projects and select the Visual Studio Drop Down -> Create AddOn Project. Currently I do not see the Visual Studio drop down as mentioned in this document.
Does this option still exist in newer version of Acumatica? If so, how do I access it? If not, does anyone know what type of project I need to create in Visual Studio to manually do what this option did?

An Add-On project is a visual studio solution containing your Acumatica extension in the form of a dynamically linked library. You can access it by opening the Project Editor for customizations and going to the Extension Library menu.
Updated Acumatica training documents are available at the following URL:
http://acumaticaopenuniversity.com/courses/

Related

Visual Studio 2022 - File Add New Item CSS, HTML, JS missing

I have 2019 Web Project I'm trying to open in Visual Studio 2022 and it's missing a lot of common file types, HTML, CSS, JS and Text to name a few. If I open the project by going to File -> Open -> Folder the expected file types are available but the Azure Dev Ops integration doesn't work.
Any pointers on how to get this working. Someone recommended building the New Item file templates but that seems like a chore for such a simple set of file types.
Update: If I change the Solution Explorer view to Folder View then I can add the files I expect, but with Folder View I can't check-in or publish. I will need to toggle between Solution View & Folder View complete those actions. To clarify further, how/what populates the Solution Explorer(Solution View) -> Add New Item menu?
In Visual Studio 2022, the .NET Framework project and item templates are now optional components. At the time of installing VS 2022, you need to manually check this option on the ASP.NET and web development section. If somehow this got missed during the installation, you can enable it by following the below steps:-
Open Visual Studio Installer
Click on Modify
Expand Asp.Net and web development
Check .Net Framework project and item templates
Screenshot:-
The above steps will bring back the missing HTML, CSS, JS, and other templates
One of the workaround you can follow to resolve the above issue,
We are trying the same with console application and trying to add html and can able to get it as well using VS-2022 with version 17.2.6.
Make sure that you have open the correct project in your environment.
HERE ARE THE SCREENSHOT FOR REFERENCE:-
Alternatively if you want to add an item template to the Add New Item dialog box in visual studio please refer this MICROSOFT DOCUMENTATION| How to Create item templates
For more information please refer the below links:-
SIMILAR SO THREAD|Can't find ADO.net Entity Data Model template in VS2017 .
This is a pain. It happened to me with the last upgrade. To fix it, open the installer, select "Web and Cloud", then "ASP.NET and web development." Check all the boxes through Intellicode, and then check ".Net Framework project and item templates".

Could not find type 'Microsoft.Office.Tools.Ribbon.RibbonTab' error prevents designer from opening

I have a VSTO for Excel project with a custom ribbon tab. The solution builds without errors. I can run the solution. It launches Excel and displays the custom ribbon tab and task pane without any issue.
When I try to open the designer for the custom ribbon tab in Visual Studio 2019, I get the following error:
Could not find type 'Microsoft.Office.Tools.Ribbon.RibbonTab'. Please
make sure the assembly that contains this type is referenced. If this
type is a part of a development project, make sure that the project
has been successfully built using the settings for your current
platform or Any CPU.
The solution builds and runs without any issues.
When I expand the error info, There is no stack trace or error line information available for this error.
The build settings are set to 'Any CPU'.
The assemblies that contain 'Microsoft.Office.Tools.Ribbon.RibbonTab' are included in the project references. These are Microsoft.Office.Tools.Common and Microsoft.Office.Tools.Common.v4.0.Utilities.
I have tried to Clean, Rebuild, and Restart Visual Studio 2019. This had no effect.
I could not find anything definitive when I Check Windows Forms Design-Time error list.
Would anyone know how to address this issue so that I can open the custom ribbon in the designer?
Is VSTO still supported by Microsoft? All documentation appears to be several years old.
This is a Visual Studio issue, not a C#/Build/DLL linkage issue.
Make sure your Visual Studio setup (do the Modify in the installer (#1) if already installed) has these two components checked:
Is VSTO still supported by Microsoft?
They are moving to an online office365 addin (my words) type VSTO. As to new features, not recently. One can still put in a Visual Studio support ticket if you have the right subscription.
I have never had any issues with ribbons, but sometimes the winforms res files in designer do not show and I use the JetBrains Rider editor to view those controls when VS fails.

How to upgrade a SharePoint 2010 Project to SharePoint 2013 (WebParts, MasterPage, App Page, User Controls) in Visual Studio 2012?

We have a SharePoint 2010 project solution which we are trying to uprgade to SharePoint 2013. This includes webparts, application pages, user controls, masterpage, etc.
Foll. is the procedure we follow, please add to it/comment if we have missed out anything:-
Open your project solution file by right clicking and choose open with VS2012.
Edit your .csproj file and add to it -> <TargetOfficeVersion>15.0</TargetOfficeVersion>
Go to VS2012 and reload you project, Go to project properties and set framework as 4.5
Go to package and under properties of the package set the version to 15.0
Do a find replace for 14.0.0.0 to 15.0.0.0.
Check each file to do a check for any hive references. You'll need to add a /15/ to these. EG: _layouts/ to _layouts/15/ and also for CONTROLTEMPLATES
For master page project make sure you copy paste the SP2013 seattle masterpage from Designer and use it in VS project.
If you are using AJAX control toolkit then make sure you use version 3.0.30930.28736 as this worked well. If we tried using AJAX version 4.5 then the webparts do not work when deployed.
Do right click on project and Click Clean to clean solution
Build the solution, then Deploy your projects.
Please add to this if there are more points to be considered. Thanks.

Visual Studio 2012 Windows service .vdproj project migration

I'm trying to move a solution I have over to Visual Studio 2012 and one of the project types is .vdproj.
According to this link this project type is not supported in Visual Studio 2012:
MSDN says they recommend that you use InstallShield Limited Edition for Visual Studio.
The problem is, when I open up my solution in VS2012 and try to add a new "Enable InstallShield Limited Edition" project to my solution, I get an error message saying:
Creating project 'test'...project creation failed.
Why might I not be able to add a project of this type to my solution?
If I make a new empty solution I can't make an InstallShield project it in either.
I'm going to try to download InstallShield limited edition and see if it does anything.
I tried out that InstallShield download, and it added two extra project types, but I'm unable to create either of them. I'm able to add normal website projects to my solutions just fine, but not deployment projects.
The installer was named the same, but this one prompted me to re-start. After re-starting I was able to add an InstallShield project, but it gets created in its own solution. So, it looks like now I have to figure out how to use it, and I'll be good to go.
It's looking like the limited edition doesn't have support to install Windows services.
This will probably be long and boring because there's lots of steps, but I'd like to write up how to move from a Windows service installer .vdproj to the new InstallShield LE that's available in Visual Studio 2012.
Step 1: Create a merge module (.msm)
Follow the steps of this guide.
Notes:
You will need to install WiX 3.6 and isWiX
The latest release of IsWiX doesn't enable the Tools menu item in Visual Studio 2012. Edit the file: C:\ProgramData\Microsoft\MSEnvShared\AddIns\IsWiXAddin.Addin (XML) and clone the HostApplication element and update 10.0 to 11.0.
In step #8 of the guide, it references a code tab. This has been moved to the XML Editor item in the bottom of the left menu
I left the MergeRedirectFolder empty for my installation
Here is my isWix files view:
After you're done with the guide you should have an empty .wxs file that looks something like this:
Using the Component XML element pulled from here you should end up with a .wxs file that looks like this:
Hit build and you should now have a .msm file.
Step 2: Adding merge module to InstallShield
Go though the wizard to setup the basic install information like company and version information.
Find the redistributables view in ISLE. Right click the list and select browse for module. After your module is found and added, right click the modules and select properties. Set the destination folder drop down to INSTALLDIR. I had to set mine to the lowest level folder I created for my install path, so you might have to experiment a bit.
Build Project, and test on virtual machine
Redistributables Screen
If you're getting errors about the path being too long you might need to change the release location to something close to the root.
Here's a list of all the build errors for reference.
Now you should be able to run your installer and have it install/start a Windows service. A lot more work than .MSI files, we got it to generate in Visual Studio 2010, but overall it was not too bad.
While there is no easy or truly supported solution for Visual Studio 2012, Visual Studio 2013 users can get an extension from Microsoft in the Visual Studio Gallery.
I found this post which says you must download InstallShield first. It's a very confusing way to work. I suggest to vote up the post on the connect site and give them comments letting know how poor that is. They could at least give a more descriptive error http://connect.microsoft.com/VisualStudio/feedback/details/732196/project-creation-failed-for-installshield-limited-edition#tabs

Is it possible to download source tree from TFS Azure without using Visual Studio?

I'm looking around mysite.tfspreview.com and I can view individual files, but I couldnt find a download all or get solution option.
So if a colleague doesnt have Visual Studio 2010 available and they wish to download a solution from TFS Azure preview what are the available options?
You should be able to use the command line client in the Microsoft Team Explorer Everywhere 11 Beta. It's not a big download (11MB), but I don't think there is a way to download a source tree directly from tfspreview without a client unless a zip has been added. Other source control services work this way (github, jira etc)
You don't need visual studio, but you need Team Explore which is add-on for Visual Studio or can be stand alone, it exists on the TFS media (DVD) or ISO, once you install Team Explore, you can access TFS Preview using GUI or Command line, you can also install TFS Power Tool 11 Beta, that will give you windows shell integration, so the context menu of the windows (when right click) it will has command to interact with TFS, as #Simon said, you can install Team Explorer Everywhere 11 Beta, but this for none windows OS or for add-on for other IDEs
Visual Studio Online has provided a means to do this (partly). On the website, navigate to your project's 'CODE/Explorer' tab. Right-click on whatever source directory/branch you wish and click the Download as ZIP menu item.
This will download a snapshot of whatever it is you selected. While extracting this won't "magically" link the files back to Visual Studio Online (ie, changes made will not be able to be committed directly from Windows Explorer, etc) or give you direct access to history; it will retain any source control bindings in any Visual Studio projects. This may be a good or a bad thing, depending on your circumstances.

Resources