I have developed a custom control flow task component, just want to check if there is any specific process or way in which if we redeploy the second/later versions of the component then we need not reset toolbox and add the component manually to the Toolbox? As of now if I make any changes to the custom component and redeploy, I have to reset toolbox and readd the component in BIDS.Which is causing problems.
Thanks in advance
Sai
Fix the assembly version, so it does not change with every deployment.
I.e. if your AssemblyInfo.cs specifies assembly version 1.0.*, make it e.g. 1.1.0.0, and don't change it, except between major incompatible releases.
Related
In my current application, there is a component called "dropdown-component" which is used across the application, I have to use "custom-dropdown-component" instead of "dropdown-component". I will not be able to do the changes to every file where ever its called as there is some specific business requirement. These changes should be reflected at the time of render. Kindly help with this
Current code
<dropdown-component></dropdown-component>
Expected to change at the runtime
<custom-dropdown-component></custom-dropdown-component>
I don't think you can change the component at runtime without major changes to the whole code.
Probably the simplest solution would be to do a search/replace or you can create the custom-dropdown-component but call it dropdown-component instead, then you you have to import the Custom Module but this is also kind tricky and not a nice solution
As far as I know I've always been able to update cshtml files and immediately see changes (upon refreshing browser) without having to stop my project.
But as I am creating a new project I see this new option to enable this feature and I'm wondering what it is because, after all, I've always been able to do this. But as far as I can tell it does exactly what it says... as if I wasn't able to do this in the past?
But I also notice now that when I make a change to a razor page, it takes a looot longer to see the update as Visual Studio recompiles the project.
What... is... going... on?
As far as I know I've always been able to update cshtml files and
immediately see changes (upon refreshing browser) without having to
stop my project.
Yes.Before asp.net core 3.0,you could do it by default.After asp.net core 3.0,you could install the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation NuGet package to enable runtime compilation.
1.Install the Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation NuGet package.
2.Update the project's Startup.ConfigureServices method to include a call to AddRazorRuntimeCompilation:
services.AddControllersWithViews().AddRazorRuntimeCompilation();
Reference:
https://learn.microsoft.com/en-us/aspnet/core/mvc/views/view-compilation?view=aspnetcore-5.0&tabs=visual-studio#enable-runtime-compilation-in-an-existing-project
Update:
From asp.net core 3.1,you could select the Enable Razor runtime compilation checkbox in the Create a new ASP.NET Core web application dialog:
I am running into a strange issue. I built an ASP.net Razor project with a Kendo UI Grid. When I first built it, I made a direct reference to the Kendo.Mvc.dll, and all was good. But I need it to be referenced by a NuGet package. However, when I switch the reference, it no longer recognizes Html.Kendo().Grid. I have tried moving the namespace reference from the Views/Web.config to the main web.config as well, but no luck. The error message I get is:
Compiler Error Message: CS1061: 'HtmlHelper' does not contain a definition for 'Kendo' and no extension method 'Kendo' accepting a first argument of type 'HtmlHelper' could be found (are you missing a using directive or an assembly reference?)
Is it possible that something in the larger NuGet Telerik.UI.for.AspNet.Core package is overriding something in the base Kendo.Mvc.dll? Or does my namespace need to be moved somewhere else? Any help would be appreciated.
Kendo UI Core does not include certain widgets, the Grid being one of them, nor does it include the server side wrappers so the Razor helpers such as Html.Kendo().Grid will not work. Hence using the Core package available via NuGet cannot be used for what you need. So the simple answer to your question is, unfortunately, no.
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.
I have been trying to create background tasks in my universal app solution. As separate Windows Runtime Component project is required to contain background tasks, I have add one to my solution. In the tasks I am accessing a class that resides in my shared project and in order to do so I use add as link. Although there seems to be no errors when I try to compile the project I get the following errors.
"winmdexp.exe" exited with code -1073741819.
Metadata file 'C:\...\BackgroundTasks.winmd' could not be found...
I believe it might be caused by the fact that the classes that I add as link doesn't have the same major namespace as background task project.
Does anyone know a solution to this problem.
Thanks in advance.
As stated in Creating Windows Runtime Components in C# and Visual Basic, all public types must have a root namespace that matches the assembly name. I believe by adding a class as a link to my Windows Runtime Component project, I broke the same root namespace restriction and as the project didn't compile successfully metadata file was not created.
In order to solve this problem at first I changed output type of my project to class library and it compiled without a problem. Unfortunately background tasks didn't run when I tried to trigger them from lifecycle events.
So in the end I moved the classes that was shared between my "Shared" and background tasks project into a class library project and this solved my problem.