Trying to add Newton.json & Restsharp in SSIS's Script task. But while adding I am getting a warning message also the script not working. An attached screenshot will add more points to this question.
These SSIS script projects are temporary, so anything you install via them (that is nested under them) disappears each time you exit the project. Any third party .dlls need to be in a shared area and registered via gacutil and then the reference put in the temporary project instead of installed in the temporary project.
Related
I deleted a version of a library, and now I'm getting the error "Library with identifier XXXXX is missing (perhaps it was deleted?)". I am also unable to remove the reference to the library. My code now won't run due to the aforementioned error. How can I resolve this?
I figured out how to accomplish this.
1. I need to be owner of the project that has the reference I'm trying to remove
2. Backup the code
3. In Script editor, open the project that has the reference I'm trying to remove
4. Select File - Delete Project
5. Close Script Editor
6. Create a new project, and import the previous code
7. Select Resources - Library to re-add the reference to the library
In SSIS online test, I got this question.
Breakpoints cannot be set to:
1. Task,
2. container,
3. package,
4. script task.
Help, please.
To score the point, select "4. Script Task" but as others have stated, that really is a poor question.
Before I begin my explanation, please note the difference between a "Script Task" and "Script Component." The Script Task is used on the Control Flow. The Script Component is used inside a Dataflow. The Script Component was not able to be debugged using breakpoints in SSIS 2008. This changed with SSIS 2012.
However, the question mentions Script Task. To my knowledge, Script Tasks have ALWAYS been able to hit breakpoints. We just need to take some steps to enable it.
Set the SSIS Project's "Run64BitRuntime" propery's value from its default True to False.
Edit your Script Task with "Edit Script" and save it again. This will help your script task code to be compiled as 32bit.
Once both your project and script task are compiled and executing in 32-bit mode, the breakpoints will be hit. See here for more information.
I'm creating a new SSRS report in AX2012. At first, I added some Data Methods through Visual Studio, but later I found another way to get what I wanted without using those data methods. Consequently, I deleted the Data Methods and the Business Logic project.
Now, everytime I build the report, I get a warning :
Could not resolve 'projectname' from the AOT. If the reference is required in your code, you may get compilation errors.
How do I delete the reference to the business logic project? My report runs without problems, but I would like to stop getting this warning...
Thanks!
It should just be a project dependency.
See here: https://msdn.microsoft.com/en-us/library/et61xzb3.aspx
To remove:
In Solution Explorer, select a project. On the Project menu, choose
Project Dependencies. The Project Dependencies dialog box opens. On
the Dependencies tab, select a project from the Project drop-down
menu. In the Depends on field, clear the check boxes beside any other
projects that are no longer dependencies of this project.
EDIT: Another option is to export the XPO and edit it in there, and reimport.
We have a requirement of creating several Windows 8 apps for tablets. There is a common solution and news apps are created by passing different resource to the same code.
For Mobile it was a cakewalk - Used the Microsoft.Build.Evaluation.Project class to get the xap file.
But for Surface, building from code does not give the direct appx output, while building using MSBuild gives appx as the output.
I tried several methods to avoid calling MSBuild from C#(by creating a Command Process) like creating a zip file - myapp.appx - and then signing it using this c++ code. It didn't workout because of an extern reference and I gave up.
Then I tried to use SignTool.exe by creating a Command Process in C#. That too failed.
So, I am wondering if there is any way to build an appx directly from C# without MSBuild.
The reason why I am trying to avoid MSBuild is to get a status from the build process, which Microsoft.Build.Evaluation.Project.Build() provides.
First try adding a pfx key to your project and then try the build via Microsoft.Build.Evaluation.Project.Build() again. The pfx is required from what I read:
See Candy's answer here:
MSBuild target to create the .appx package
So then the trick would be to use SignTool to get the pfx in the first place and update the project with that pfx, but first see if the above works.
I am writing a WIX installer and I have a following requirement:
During installation, I need to pass an absolute path to a file (lets call it A) included in my installer to a COM component, which already exists on the hard drive and is a part of another program. I have already written an appropriate Custom Action which expects a path to the file A. I don't want to include A as a file installed in the Program Files folder and removed during the uninstallation process. Instead, I would like to put A only temporary on the hard drive, call my Custom Action which will cause the COM component to use the content of A, and then remove A from disk. Is there an easy way to accomplish this goal?
I have tried to utilize the Binary Table and store A there, however I don't know how to reference A using absolute path. I know I could put A outside of MSI file but I would like to keep every file installer needs in a single MSI.
Any help would be appreciated.
Deleting a file that MSI installed means that MSI will consider it "broken" and try to auto-repair it if called on to do so. That happens automatically in several cases (e.g., advertised shortcuts and COM registration) so I'd recommend against it. Leave the file there instead -- it's done its job and there's no harm in leaving it there.
I would take this approach.
Install the file "A" into any directory. Run your custom action needed to update the COM component. Then run another custom action or modify the currently written one to remove the file after it is no longer in use. This would leave no trace of the file "A" and if you schedule the custom action to only run during the install you won't have to worry about it on uninstall.