i'm trying to create custom command for autocad but i have the following setup:
- i have visual studio 2013 and 2015 both installed in the same order
- i have autocad 2015 and 2018 both installed in the same order
i am new to this so correct me if i am wrong about the requirement for this
-in order to create custom dlls for acad 2015 we need vs 2013
-in order to create custom dlls for acad 2018 we need vs 2015
when i load dll created in vs 2013 in acad 2015 it works fine
but the problem is when doing the same for acad 2018
it show's nothing on acad console (meaning nothing happen in the loading process) but when i type my command nothing shows up
i am sure there is a way to check if a dll is successfully loaded from some log some where i just don't know what and where
if any one know what i am talking about please help
thank you
The easiest way to tell if something loaded correctly is to add an Editor.WriteMessage("Insert message here...") into the end of your Initialization function.
If the DLL loads correctly from a NETLOAD command or from your Bundle configuration, the message will be displayed on the command line.
Related
I tried reinstalling, modifying, but still no luck...
The other CLR options don't work and always give errors.
enter image description here
I suggest you should check whether you have installered the C++/CLI support. Open the VS Installer window, you could click on "Individual Components", then scroll quite a ways down to get to the "Compilers, build tools, and runtimes" section. In there, you'll find a list of components for c++/cli support. You could choose the version you need to install.
For more details about create CLR empty projects, I suggest you could refer to the Doc: How to: Create CLR Empty Projects
I had VS 2019 installed and was working on a 2019 solution with 2019 projects in VS 2022. I had to install CLR (CLI?) support for 2019 as well to get them to show up, even though I was running VS 2022
I have a project in Visual Studio 2017 with .NET Framework 4. For reports I use the RDLC designer, but I have a problem. The designer creates the reports using RDL 2016 and I need you to use the 2010 definition.
Can I configure this?
I need it since the program has to be compatible with Windows XP and there is no ReportViewer Runtime that supports RDL 2016 for Windows XP.
I had the same problem, but if a did a new report it was all right, the new report was created and saved with the old schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2008/01/reportdefinition". (report viewed with a text editor)
When I added a parameters and re-saved, VS turned the schema in
new schema:
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2016/01/reportdefinition"
But I found a solution that work also with Windows XP:
I install all necessary to manipulate the report with VS 2017 (in Visual studio 2017 are all external plug-in), then change the reference of my project e take 2 new referenze to this DLL:
1)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.WinForms.dll
2)
..\project\packages\Microsoft.ReportingServices.ReportViewerControl.Winforms.140.340.80\lib\net40\Microsoft.ReportViewer.Common.dll
After that all work.
This new version of DLL handle both "old schema" and "new schema"
You can check ReportViewer version and installed in your Visual Studio 2017 using PM>
(Before doing this you have to delete previous Report viewer references )
https://www.nuget.org/packages/Microsoft.ReportingServices.ReportViewerControl.Winforms/140.1.291.2731477-rc
This package Manager work for me.
PM>Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc
Reporting solutions in VS have always been tied to the version of SSDT that is current at the time of release. e.g. VS 2015 only supported the Sql Server 2016 report schema.
I think the answer is that you might be able to do something to change the schema it uses by editing the XML directly, as suggested by Ricky A, but for proper, designer support this isn't going to work.
Article from Microsoft on schema versions supported here doesn't mention anything other than schema v2016 support in VS 2017: https://learn.microsoft.com/en-us/sql/reporting-services/plan-for-report-design-and-report-deployment-reporting-services
I am fairly sure that your VS licence will cover old versions, and different versions live happily side by side, so install whichever other version you need for the reporting project you are editing (along with the correct version of SSDT/BIDS etc).
Although too late, but I have fixed this issue by installing this package :
Microsoft RDLC Report Designer
Install-Package Microsoft.ReportingServices.ReportViewerControl.Winforms -Version 140.1.291.2731477-rc this saved my ass
I have an Excel Add-In for Excel-2010 version, which was created using Microsoft Visual Studio 2010.
The code is written in C#. To install the Add-In , you have to run a setup.exe file which will add the Add-In to Excel.
Everything seems to be working fine on Excel 2010, but when I am trying to install this on Excel-2103
I am getting the following Error:
The Office 2010 Shared PIA System is not Available.
Is there a way to install the add-in in the 2013 and also after it is installed will it work Perfectly or do i need to make any changes ?
It took a while to figure out but its done finally.
The add in launch conditions were checking for the availability of the shared PIA.
Condition: HASSHAREDPIA
and it was looking for the corresponding component id associated with excel 2013 PIA component ID
Click Here https://social.msdn.microsoft.com/Forums/vstudio/en-US/1fd8690a-812c-49f9-a77e-e19f24de7c4e/office-2013-pia-component-ids?forum=vsto
to obtain the suitable component id and replace it in the
Search Target Machine
Search for office 2010 shared PIA.
and replace the component id.
the add in should be working fine.
I'm using Visual Studio 2012 Express for Web.
When I try to add a view, I get an error saying:
The templates had the following 1 error(s)
C:\Program Files\Microsoft Visual Studio
11.0\Common7\IDE\VWExpress\ItemTemplates\CSharp\Web\MV
C 3\CodeTemplates\AddView\CSHTML\Empty.tt(-1,-1): error :
There was a problem getting an AppDomain to run the
transformation from the host. The process cannot continue.
I've been plugging in Ninject (this is actually just an app to prove it's working) so it could be something to do with one of the start-up files.
Where do I start looking to try to fix this?
Thanks
Dave
Try restarting the Visual Studio 2012 and add a view now, and that should do for you.
Have you copied the Code Templates folder your project ?
Restarting didn't work for me. It turns out that mvc3 had never been installed on my machine (mvc4 was in place already) and also my copy of visual studio wanted to install service pack 1. So I uninstalled the newer version of newget using the control panel restarted visual studio. The service pack (sp1) successfully installed. Now my custom .tt files successfully render new views.
Information that led me down this road:
http://forums.asp.net/t/1820254.aspx?MVC+Add+View+Model+Controller+from+template+throws+an+error
and
http://forums.asp.net/t/1729674.aspx?Installing+MVC3+after+Installing+MVC4
I have SQL Server 2012, SSIS, SSDT and Visual Studio 2010. I can create a new SSIS package and add a Script Task, but if I attempt to open the Script Editor for that Script Task I get the following error:
TITLE: Microsoft Visual Studio
------------------------------
Cannot show Visual Studio 2010 Tools for Applications editor.
------------------------------
ADDITIONAL INFORMATION:
Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications.Core, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. (mscorlib)
------------------------------
BUTTONS:
OK
------------------------------
From my own investigation into this error, I found that Visual Studio Tools for Applications appears to be a part of MS Office 2007 and higher. This seemed like an odd dependency for to have, but I installed MS Office 2010 just for grins. It didn't change anything. What else should I try?
You will also get this error, if you are trying to debug a script task in VS 2010 and Run64BitRuntime is set to true. In order to debug, set it to false.
I was getting this error and nothing I came across corrected the problem until I logged off as my normal user and logged in as my local admin user. Once I logged in as an admin I could edit the script in my package. Once I logged back in as my regular user the edit script button worked for it too.
I assume it needed to register the assembly on the first launch and couldn't with my regular domain user.
I also got this same error when trying to open the Script Editor, but for a different reason. Not sure how it happened, but I had 3 copies of VSTA (different versions) installed. Once I removed all of them and re-installed SQL Server 2012, problem solved. Hope that helps.
For me the solution was:
close bids (I'm on 2008r2)
reopen
edit the script (it allowed me to edit it once after restarting bids)
delete all breakpoints
make a trivial change, such as adding a blank line
save
That solved it for me.
This worked for me without doing any kind uninstall.
My environment:
Microsoft Visual Studio 9.0 (2008)
Solution:
Go to cd "C:\program files (x86)\microsoft visual studio 9.0\common7\ide\"
Execute command vsta.exe /setup /hostid SSIS_ScriptTask. This will open VSTA with blank project. Let it open and then close it.
Execute command vsta.exe /setup /hostid SSIS_ScriptComponent. This will open VSTA with blank project. Let it open and then close it.
Open your solution/packages that contains the script task.
Click Edit button in Script task and it should open now. Just in case if it dont, I would suggest to keep the blank vsta of step 2 & 3 open and then click the Edit button in script task.
Took almost two hours and thankfully it worked for me. I did not have admin right to perform all that nasty uninstall and registry edit solutions.
Hope it helps someone!!!
Reference : http://blogs.msdn.com/b/jason_howell/archive/2010/08/18/vsta-setup-and-configuration-troubles-for-ssis-2008-and-r2-installations.aspx
Cannot show Visual Studio 2010 Tools for Applications editor.
Just follow the below solution:
Go to SQL Server Setup folder.
Inside that folder "redist".
Under that one more folder "VSTA".
Under VSTA folder "X86" and "X64"
Install the VSTA_RT30.
It works fine.
I figured out my problem this morning. When I uninstalled SQL Server 2012 (and the remnants of 2008 left behind when I upgraded last month) I also uninstalled 3 packages that were actually part of Visual Studio 2010. Had I not done this, a reinstallation of SQL Server 2012 would probably have done the trick, but instead I found new errors. When I reinstalled these 3 packages from the Visual Studio 2010 distribution media, everything started working.
The 3 packages in question were:
Microsoft SQL Server 2008 R2 Data-tier Application Project
Microsoft SQL Server 2008 R2 Data-tier Application Framework
Microsoft SQL Server 2008 R2 Transact-SQL Language Service