I'm looking at sample code here:
https://blogs.msdn.microsoft.com/paolos/2010/01/29/how-to-boost-message-transformations-using-the-xslcompiledtransform-class/
But I can't get the helper routine to compile because this statement:
using
Microsoft.BizTalk.CAT.Samples.DynamicTransforms.Helpers.Properties;
is giving error:
The type or namespace name 'Properties' does not exist in the
namespace 'Microsoft.BizTalk.CAT.Samples.DynamicTransforms.Helpers'
(are you missing an assembly reference?)
If I comment that line out, then I get errors on the class "customBTXMessage" (the type or namespace ... cannot be found...)
That sample is for BizTalk 2010.
You should not need to do that for BizTalk 2013 and up, as it already uses XSLT Compiled transform.
This actually caused a few problems as per Known issues in BizTalk Server 2013
To run lots of map for testing purposes I would use BizUnit
Related
I've added 3 default Blazor projects to my solution.
Blazor WebAssembly1
Blazor WebAsssembly2
Blazor Server
The first WebAssembly project is converted to a razor library in order to share code between server and webassembly projects. I also deleted the default pages like FetchData.razor and such.
On compilation I still get compile error on this (the app runs fine though), and I can't seem to resolve them. I've search through the entire solution but can't find any of the files that results in the compile errors.
How to locate the reason for the errors and remove the references? The files are deleted from the project.
Example of compiler error:
CS0246 The type or namepace 'WeatherForecastService' could not be found (are you missing a using directive or an assembly reference?)
The errors in FetchData indicate a problem with the using statements.
Try to check if you have global using, try to remove and declare explicit in the razor page.
Check your CSPROJ and verify the project type, in the RCL the type must be:
<Project Sdk="Microsoft.NET.Sdk.Razor">
In the RCL you haven't a Program/App structure, you have only components and wwwroot elements.
My RCL is composed as follow:
I have also a _Imports.razor with:
#using Microsoft.AspNetCore.Components.Web
...
The issue resolved itself when I restarted Visual Studio.
Sorry for the wild goose chase
We are trying to use Microsoft's OData Client to generate C# classes for our custom entities in Microsoft Dynamics. We add the "OData Connected Service" extension to Visual Studio and connect to the Dynamics $metadata endpoint to generate the client code, as per the instructions.
We end up with over 1,100 source files generated and well over a million lines of code. Sometimes the code generation crashes Visual Studio. Another time we got an Out of Memory exception. This happens even when we limit the generated entities to our own custom entities in Dynamics.
The worst part is the generated code does not compile. The most common compiler error is:
The type or namespace name 'RelationshipAttribute' does not exist in the namespace 'Microsoft.Dynamics.CRM' (are you missing an assembly reference?)
Here is an example source code line that causes this error:
private global::System.Collections.ObjectModel.Collection<global::Microsoft.Dynamics.CRM.RelationshipAttribute> _RelationshipAttributes = new global::System.Collections.ObjectModel.Collection<global::Microsoft.Dynamics.CRM.RelationshipAttribute>();
Does anyone have an idea why this is happening?
I'm new to Visual C++. I have two separate projects (let's call the first Converter and the second TreeGridView). I have this line of code in the Converter project:
private: AdvancedDataGridView::TreeGridView^ treeGridView;
which throws this error on 'AdvancedDataGridView':
name followed by '::' must be a class or namespace name
I think I understand the error - Visual C++ can't find a class or namespace called 'AdvancedDataGridView' right?
I have a separate Visual Studio project called TreeGridView which has 3 C# projects included in it. One of the projects has an assembly name of 'ExpandableGridView' and a default namespace of 'AdvancedDataGridView' and an output of type Class Library. Another project has an assembly name of AdvancedDataGridView and a default namespace of AdvancedDataGridView and an output type of Windows Application.
Being new to Visual C++ and the codebase I'm using, I'm not sure how to make the error go away. The TreeGridView project (the one with 3 c# projects) does generate an ExpandableGridView.dll file which I've added a reference to in my Converter project, but the error persists. Intellisense doesn't find AdvancedDataGridView at all. Any ideas?
Additional info: When adding the ExpandableGridView.dll as a reference, I get a yellow warning triangle icon on the reference and 'Full Path' in the properties says
The "Microsoft.VisualStudio.ProjectSystem.References.UnresolvedAssemblyReference" reference
could not be resolved.
Solved. I had two references to the same ExpandableGridView dll file - got rid of both of them, then added the latest dll again - after that the error and warning I mentioned above went away.
You're trying to XOR a type with a variable? Pointers are declared using type*, not type^.
See http://www.cplusplus.com/doc/tutorial/pointers/ for a tutorial on C and C++ pointers.
I have successfully installed DNN 8 and all configuration.
i am also referring video to develop module in visual studio.
https://www.youtube.com/watch?v=AKCYRPuoXF4
when i am trying to build the project then
error comes like:
Error 17 The type or namespace name 'DotNetNuke' could not be found
(are you missing a using directive or an assembly
reference?) C:\websites\dnndev.me\DesktopModules\MyDNNModule\MyDNNModuleModuleSettingsBase.cs 13 7 MyDNNModule
Please help to solve that.
thank you in advance.
Working with DNN8, sometimes I get a set of errors with message
The type or namespace name 'DotNetNuke' could not be found (are you
missing a using directive or an assembly reference?)
, probably 10 or 15 of them, and all located on top of one ascx file. (My dotnetnuke.dll is correctly placed in DNN's bin folder). Taking a better look (scroll down!), I can see that - except them - there are some more error messages (maybe just one of them), and that those additional errors are perfectly clear and logical. So I correct my source code in order to avoid those additional messages, and when I do that - those problematic messages also disappear!
In my case it took me a while to find the solution to this problem, since it only got triggered when I made a change to the View.ascx file.
You need the Visual Studio project to target framework to 4.5 instead of 4.5.1.
I got this solution from here.
Make sure to add a Reference to dotnetnuke.dll in the c:\websites\dnndev.me\bin folder
I honestly haven't done anything with DNN 8 CTP yet, I would stick with 7.4.1 until 8 is official released.
I am upgrading MOSS2007 solution to SP2013. Everything is fine When I am building the solution at that time it is building successgully.
But when I am trying to publish the solution at that time it is throwing following error:
The type or namespace name 'xxx' does not exist in the namespace 'xxx' (are you missing an assembly reference?)
I have tried many things but no luck.
Is there any solution for this error?
When you have created your solution you may find that you have built the solution on a environment where a certain DLL exists.
Realistically what you need to do is look at your error message and look in to what DLL contains the namespace that the error is giving you the error and check that the DLL exists on all Web servers, Possibly app server(depending on farm set up)
Cheers
Truez