guys. I am using jaspersoft studio 5.6.0 final.
I am having a weird issue that whenever I made new changes to my own functions library. jaspersoft studio DOES NOT recompile it automatically. If I clean and build the project manually, the generated report won't take advantage of the new changes.
It happens to me (using windows7) and my teammates (using mac)
As a result, I have to restart the whole program all the time.
And, even if I do that, my function library sometime works and sometime don't. (no idea why)
Hope anyone can help me. Thanks a lot.
To solve this isuue you should enable build automatically
on the top click on project and check build automatically
Related
Currently I am trying to use Visual Studio Code with Ionide to build a F# Solution. To describe my problem, i first describe what i have done, and what works.
I created a solution with two Projects. One Project is a Queue that contains a F# library. Another project is Queue.Test that is a console application that uses the Queue library, and should contain the Tests for the Queue library.
I'm using .Net6 and created the solution and Project with the dotnet cli tool.
In general, i can build the project with dotnet and i also can use everything in Visual Studio Code. I load the Folder that contains both projects, and Visual Studio Code loads the library.
I am able to edit the Library and my Console application. In my Console application i also can access the Queue and so on. Autocompletion works, and so on.
But, there is one problem. When i add a new function to my library, let's say Queue.help then in my Console application, i cannot see that function. It doesn't show in autocomplete, and when I write code that uses that function i get a compiler error telling me that function doesn't exists.
I can Build/Rebuild from VS Code or from CLI but the problem goes not away.
The only way Ionide starts to see the new function is by building the library AND restarting VS Code. As long i don't restart, it seems to not update the generated dll (i guess).
This is sure annoying, as i don't want to reload/restart VSCode everytime I add a new function to my library.
So my question: How i can I fix this?
What i want is to be able to change my library, and at the same time write tests in the other project and get full Code autocompletion.
Does somebody else have the same problem, or should I change my workflow?
What can i do, to debug this problem on my own?
Some tips?
This issue is fixed by the recent version of Ionide 5.10.1
I've been working on a project template today, first time doing so but it has been going alright. I'm almost finished but have now run into some weird issue I can't figure out.
For some reason which I don't know, whenever I try and debug my project template it is now stuck to using some old version of it. No matter what or how much I change then rebuild and try to debug - it still uses some weird old version stuck in some sort of limbo.
I can't seem to figure out where it's finding this file, I've cleared my temp folder. It doesn't show up as installed when I go to Manage Extensions in Visual Studio.
Any ideas what might have happened? There are no errors or warnings.
I was able to solve this by deleting all files inside %LOCALAPPDATA%\Microsoft\VisualStudio\16.0_cfa111feExp\Extensions. After doing so, I restarted VS and loaded up my project and rebuild (not build) the solution.
After that, it now shows the up-to-date version of the project template. What caused this and how to potentially prevent it in the future - I still have absolutely no idea.
I use Visual Studio 2019 Version 16.4.2
I am using Roslyn for application scripting via Nuget Package Manager. Setup should be rather simple. Create new project and, in Nuget manager, add Microsoft.CodeAnalysis.Sripting package. After couple of confirmations you are ready to go.
Next step should be checking for installed packages update. Currently, there are 5 updates that are shown after initial installation. Again, it is pretty straightforward to do this.
However, immediately after the update, two of those packages show yellow triangle in Reference node of the project.
I have tried to resolve this following SO and other hints but nothing helped me so far.
At the end, I have installed new VM with Windows 10 Pro (with all updates) and VS2017 Community Edition. After that new Windows Forms project (.net 4.6.1. based for x64) was created and scripting package is added. Unfortunately, yellow triangles are still there (after update).
Problematic packages are System.ValueTuple and System.Security.Cryptography. X509Certificates.
Also, after cleaning and rebuilding the solution, a number of warnings (MSB3836) - explicit binding redirect on "System..." conflicts with autogenerated binding redirect.
Solution to this problem might shed a light on problem with more complex solution that I stumbled upon after migration to VS 2017.
So, what is the reason for such behavior? Remember, this happens on new installation of OS and VS with simplest project possible.
Visual Studio 2017 Communnity Incorrectly Updates Roslyn Scripting
I got the same result with you steps. This issue only occurred on the Visual Studio 2017 not Visual Studio 2015. That should have some issue with package Microsoft.CodeAnalysis.
To resolve this issue, I would like provide you a workaround:
Update packages "System.ValueTuple" and "System.Security.Cryptography. X509Certificates" first, then update other packages.
It works fine on my side, you can check if it works for you.
In order to track this issue, I have create a new issue on GitHub:
https://github.com/dotnet/roslyn/issues/22290
If you have additional information to add, you can add comments below that issue. And you can check the feedback from this link.
New to Android. I'm trying to build the HelloCompute sample code for API 17 with ADT v22.0.1 under Windows 7. I do File:New Project:Android Sample Project, and select HelloCompute. In the Package Explorer I see HelloCompute.java and mono.rs in src under com.example.android.rs.hellocompute. However, I don't see any reflected layer code under gen, and I get the error "ScriptC_mono cannot be resolved to a type". I have tried re-installing eclipse / adt, and re-installing the sample code.
Is there some manual step I need to perform to generate the reflected layer?
Thanks.
I ran into a similar problem.
I got around it by running llvm-rs-cc on mono.rs and generating the ScriptC_mono.java file. Eclipse then picks up this source and compiles everything successfully.
I do not know yet whether is there a way of telling eclipse to do it automatically.
The latest ADT does have a problem in generating RenderScript code as part of the build process, so you need to do this step manually right now (or look at other threads suggesting workarounds). Hopefully the upcoming ADT will actually fix this issue so that everything gets created automatically.
Had the same problem.
Win 7 64bit.
Eclipse 4.2.2.
Upgraded to:
SDK Tools: 22.0.5.
Platform-tools: 18.0.1.
Build-tols: 18.0.1.
Problem solved.
Renderscript compilation was broken in ADT 22.0.1. Fixed for non-Windows platforms on 22.0.4. Fixed for Windows platform on 22.0.5.
I have this Metro App project that I just tried building for the Windows Store.
After completing the buildprocess (with no errors) I can't open the appxmanifest xml file in visual studio anymore. If I select "STORE" > "Edit App Manifest" I get the following error message: "Value does not fall within the expected range."
I can't open any manifest file in any project now.
Does anybody know whats happening, do I need to reinstall Visual Studio or whats going on?
I'm pretty desperate, so any suggestions are welcome.
Found the answer here http://forums.asp.net/t/1836720.aspx/ - so i tried deleting the .suo files from the project, and now it seems to work. I have no clue why that would affect newly created/other/checked out projects, weird behavior indeed?
(Since I am both new to SO and to Visual Studio, I don't know if answering my own question is considered bad practice, if it is, please let me know what I should do instead)
It's an XML file, so you could try to open it with a text editor to figure out if there's an invalid value set somewhere. You could always compare to a default Package.appxmanifest from a new project.
Can your fellow coworker open the manifesting file you're having trouble with?
The first thing to check is to make sure you are running Visual Studio as an admin. (Right click, run as administrator)
Try creating a completely new project. Save it without modifications. Build it. See if you can open the manifesting file in that project. If you can't, try a XAML/C# project instead of JS just to see if something is wrong with the specific project type.
And before you try completely reinstalling, you might try resetting your Visual Studio settings. Make sure to take a backup just in case you need to get your environment back to where it was once you find the issue.
http://msdn.microsoft.com/en-us/library/ms247075.aspx