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
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
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
I'm experiencing alot of errors on a big project i've been working on for quite a while now.
Out of nowhere, my VS2017 doesn't recognise any xamarin references.
The project compiled flawlessly a couple of hours ago.
Example
I get 119 errors because of this when i try to compile.
For a solution, i tried to uninstall a nuget package: Xamarin.Android.Support.v4, this resulted in me not being able to install it back because i keep getting these errors when i try to install the package.
I have Xamarin.Forms installed. The bug started not being able to find certain dll files from my .net framework, i tried to solve this by giving direct references to the files, but it kept on not being able to find new dll files.
I always keep a backup on Github for reasons like this, but for some reason, the github project gives me the same bugs! It didn't when i saved it last night. This tells me my environment is screwed up, and for all i've done, i only seem to make it worse, so i don't want to mess up anything more.
Error message:
The type or namespace name 'Thickness' could not be found (are you missing a using directive or an assembly reference?)
The type or namespace name 'Xamarin' could not be found (are you missing a using directive or an assembly reference?
The type or namespace name 'Xamarin' could not be found (are you missing a using directive or an assembly reference?)
The type or namespace name 'XamlCompilationAttribute' could not be found (are you missing a using directive or an assembly reference?)
(This continues for all 119 errors)
New error
Try checking your window's updates. I had the same issue a couple of hours ago and solved it with a system update
try deleting the package folder, and let it restore, Also remove Xamarin.forms nugget then install it again
this error apears only on run time not on build the build success
what is the yellow mark beside the reference mean
I have experienced this myself (the yellow), but no problem really occurred during execution. Anyways I have found some references of your problem here. The second most voted answer that includes Save, Clean and Rebuild solution seems appropriate.
Hope this helps you with your problem.
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.