I'm learning how to use Git with Visual Studio and I just noticed a file that doesn't have an extension in my local repository and I am wondering how it got there in the first place. This is how it shows if I run git status:
(Apologies for links, need more reputation to post images)
https://imgur.com/4Qw7cbn
However the file's name in the local repo appears like so in Windows Explorer.
https://imgur.com/cE0QT7W
I moved the file out of the local Git repo to see if Git or Visual Studio would throw any errors but nothing happened. I am suspecting that this is some sort of log file since when I open it I find the below inside.
Note that this is only a sample since the file is quite long.
[33mcommit 836ebc841dcc16806f4dad33d2ac32b5437b5d32[m[33m ([m[1;36mHEAD -> [m[1;32mmaster[m[33m)[m
Date: Mon Aug 12 16:11:23 2019 +0300
Add project files.
[1mdiff --git a/RandomNameGenerator.sln b/RandomNameGenerator.sln[m
[1mnew file mode 100644[m
[1mindex 0000000..f0bc8d2[m
[1m--- /dev/null[m
[1m+++ b/RandomNameGenerator.sln[m
[36m## -0,0 +1,25 ##[m
[32m+[m[32m[m
[32m+[m[32mMicrosoft Visual Studio Solution File, Format Version 12.00[m
[32m+[m[32m# Visual Studio 15[m
[32m+[m[32mVisualStudioVersion = 15.0.28307.645[m
[32m+[m[32mMinimumVisualStudioVersion = 10.0.40219.1[m
[32m+[m[32mProject("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") =
"RandomNameGenerator", "RandomNameGenerator\RandomNameGenerator.csproj", "{18AAEB05-8D77-463F-91DE-ED78FBDE4EB1}"[m
Curiosity has gotten the better of me and I want to know what it is and why it's there?
Much appreciated if anyone can shed some insight.
I'm trying to create an Addin in EA
-Assembly is made visible in COM from Assembly info
-Project is registered for COM Interop
using MS VS C# 2015, .Net 4 and EA 13. but after following all the steps in tutorial below I face this error: Missing (0x800401f3).
enter image description here
tutorial for Creating EA Addin:
https://bellekens.com/2011/01/29/tutorial-create-your-first-c-enterprise-architect-addin-in-10-minutes/
thanks for your help.
Solved this problem on my site: Win7 / EA12.1: There was a "0" as value in the registry entry for HK_CURRENT_USER. Deleting that value solved the problem. All add-ins are flagged as being "enabled" now.
Got the information from
http://sparxsystems.com/forums/smf/index.php/topic,37755.msg235804.html#msg235804
reply #6
I had a similar issue. My problem was that COM interop does not register my dll to HKEY_CLASSES_ROOT in registry. Try to check the presence of HKEY_CLASSES_ROOT/projectname.classname in your registry.
U can examine EA addins by this tool: https://github.com/EXploringEA/EAInstallationInspector
In my case tool shows me this.
When I am trying to open a axml file in Visual Studio 15 then below error is coming. I am using windows 7 OS. Any body please help on this!!
"Something went wrong"
mono.android.DesignerException
at mono.android.DesignerException.fromThrowable(DesignerException.java:43)
at mono.android.DesignerSession.checkRenderResultForError(DesignerSession.java:177)
at mono.android.DesignerSession.load(DesignerSession.java:228)
at mono.android.DesignerSession.processMessage(DesignerSession.java:693)
at mono.android.MessageListener.executeMessage(MessageListener.java:88)
at mono.android.MessageListener$Runner.run(MessageListener.java:44)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at android.content.res.Resources_Delegate.disposeSystem(Resources_Delegate.java:83)
at com.android.layoutlib.bridge.android.BridgeContext.disposeResources(BridgeContext.java:242)
at com.android.layoutlib.bridge.impl.RenderAction.tearDown(RenderAction.java:257)
at com.android.layoutlib.bridge.impl.RenderAction.release(RenderAction.java:220)
at com.android.layoutlib.bridge.Bridge.createSession(Bridge.java:438)
at com.android.ide.common.rendering.LayoutLibrary.createSession(LayoutLibrary.java:389)
at mono.android.DesignerSession.load(DesignerSession.java:222)
... 4 more
PFA the screen shot
Check your AndroidManifest file. See the minSdkVersion and download that version on SDK Manager (install "Tools" and "Extras" folder's too).
Recompile your solution and restart.
:)
I tried to compile my ASP.NET c# project with VS 2013 in Release mode but I can't do this. During the compile process I obtain some error like that one
Error 55 Could not copy
"\192.168.1.103\d$\ShareDLL\CommonTools\CommonTools20\CommonTools20.dll" to
"\192.168.1.103l\d$\ShareDLL\IndexCalculation\IndexCalculation\CommonTools20.dll".
Exceeded retry count of 10. Failed.
and then
Error 56 Unable to copy file
"\192.168.1.103\d$\ShareDLL\CommonTools\CommonTools20\CommonTools20.dll" to
"\192.168.1.103l\d$\ShareDLL\IndexCalculation\IndexCalculation\CommonTools20.dll".
Impossibile trovare il percorso di rete.
for some libraries.
The problem is that if I compile the same project in Debug mode everything works fine.
I have to set something in VS?
Thanks
I always resolve it like this:
1.Clean Solution (and do nothing else)
2.Close all open documents/files in the solution
3.Exit VS
4.Run VS
5.Build Solution
Dont know why it work, but work. (VS 2013 also)
When I try to access an Excel spreadsheet using the following code I get a "Library not registered' error when defining the workbook object wrkbuk using C# from Visual Studio 2012 with Office 2007 (ver 12) installed
Microsoft.Office.Interop.Excel.Application excapp = new Microsoft.Office.Interop.Excel.Application();
string bookname = #"C:\Users\Public\Documents\RECRUITMENT & SELECTION\MOVEMENTS\MOVEMENTS\Miscellaneous Documents\VacanciesREAL.xls";
Workbook wrkbuk = excapp.Workbooks.Open(bookname);
Worksheet wrksht = new Worksheet();
The error details are
System.InvalidCastException was unhandled HResult=-2147467262
Message=Unable to cast COM object of type
'Microsoft.Office.Interop.Excel.ApplicationClass' to interface type
'Microsoft.Office.Interop.Excel._Application'. This operation failed
because the QueryInterface call on the COM component for the interface
with IID '{000208D5-0000-0000-C000-000000000046}' failed due to the
following error: Library not registered. (Exception from HRESULT:
0x8002801D (TYPE_E_LIBNOTREGISTERED)). Source=mscorlib
I've created a reference to Microsoft.Office.Interop.Excel.dll in the Office 14 Primary Interop Assembly that comes with VS 2012 and also for the Office 12 version of the dll and neither fixes the problem. I've tried registering the dlls with regasm but this does not help either.
I can create the worksheet wrksht on the following line OK with the Office 14 and Office 12 dlls so the problem seems only affect workbook definition.
Dec 17 2013
Tried reinstalling Office 2007 to no avail but found this solution, which worked. It was at
http://social.msdn.microsoft.com/Forums/vstudio/en-US/d3f92da7-96d3-404b-89d0-d236800ceae5/vs-2012-rc-and-visual-studio-tools-for-office?forum=vsto
Problem is code from multiple versions of Office - I had code from Office 14, possibly coming from VS 2012 install
I suspect that VS 2012 RC has installed the Office 2013 type libraries, and that there are now duplicate versions registered. I got that specific error message
('unable to cast
_Application'....'TYPE_E_LIBNOTREGISTERED')
after a messy uninstall, and then re-installing an older version of Office. I solved it by following the advice of another forum thread here which I'm sadly unable to find...basically I searched the registry for the CLSID in the error message, so, {00020970-0000-0000-C000-000000000046}. Its registry key contained two keys, one of which was called 'TypeLib', which in turn contained another CLSID for the type library. I then searched the registry, starting at the beginning again, for that second CLSID, which led me to the relevant interop type library. It had two entries....8.3 and 8.4, the bigger number corresponding to the later version of Office....which I deleted...and immediately was able to run my program.
I had this exact same problem. Here's how I fixed it:
Go to
HKEY_CLASSES_ROOT\TypeLib\ and search for Office.Interop.Excel.
I found HKEY_CLASSES_ROOT\TypeLib\(guid)\1.8 but its child nodes were empty! I deleted it because Office 15 wasn't installed on that machine, and hey presto - it worked.
Either our VSTO project installer, or our own custom installer must have placed the 1.8 folder there.
I found the solution here:
Error accessing COM components
I had exactly the same issue. If you have installed a new version of Office and for some reason you have to install the older version without removing the new one (For my case I just need to install the Office XP Photo Editor) and this caused the issue.
After spending 3 hours up and down, the best way is to repair the new version of Office and everything was back to normal as it should be.
Hope this info helps provided you have the same or similar scenario.
Something which hasn't been mentioned here but which may be useful is that subkeys of 1.XX can cause issues as well. For example:
Under Computer\HKEY_CLASSES_ROOT\TypeLib{00020813-0000-0000-C000-000000000046} I had the subkey 1.9. This in turn has the subkey 0(or should). Now under this, there were two subkeys - Win32 and Win64. As a result, Visual Studio was unable to resolve the location of Microsoft.Office.Interop.Excel.dll - it was reading two subkeys where it could only read one. Deleting the Win32 subkey fixed my issue completely. Please note that this was done after a complete reinstall of VS 2017 & Office 365 Pro Plus. Hope this helps someone.
I will confirm #stuzor 's answer on two machines I've encountered.
Background:
Windows7 64 bit
Office 2010 (32bit)
Lync 2013
HKEY_CLASSES_ROOT\TypeLib\ , searched for "Office.Interop.Excel". Found the barely existent "1.8" folder. Upon deletion, the function in an old VB.net app began working immediately.
This is an answer if you can not modify or delete the regedit records. I had the same problem, in the company where I work, there are about 30 machines with office 2010 and I could not erase or open records in the regedit. because the client machine was in a domain that would not let me. although I had administrator permissions it did not allow me to delete records in the regedit. I tried to find a solution for 1 month, and I did not find it. so I had to stop using interop and migrate to OpenXml to edit excel templates and ClosedXml to create new excel. This saved my life, because my boss was already pressing me.
Open the project/solution in Visual Studio, and open the console using the Tools > NuGet Package Manager > Package Manager Console command.
and install 2 packages
Install-Package DocumentFormat.OpenXml -Version 2.5.0
Install-Package SpreadsheetLight
pd: OpenXml 2.8 dont work with SpreadsheetLight, better use 2.5.0
add this in the beggining
using DocumentFormat.OpenXml;
using DocumentFormat.OpenXml.Packaging;
using DocumentFormat.OpenXml.Spreadsheet;
using SpreadsheetLight;
in your button or class copy and modify
SaveFileDialog fichero = new SaveFileDialog();
fichero.Filter = "Excel (*.xlsx)|*.xlsx";
if (fichero.ShowDialog() == DialogResult.OK)
{
SLDocument sl = new SLDocument("c:\\bin\\est1.xlsx", "Sheet1");
sl.SetCellValue("E9", "Let's party!!!!111!!!1");
sl.SelectWorksheet("Sheet2");
sl.SetCellValue("C7", "Before anyone calls the popo!");
sl.AddWorksheet("ERTRT");
sl.SetCellValue("B4", "Who let the dogs out?");
sl.SetCellValue("B5", "Woof!");
sl.SaveAs(fichero.FileName);
MessageBox.Show("Report " + fichero.FileName + "!");
}
The registry hack described above fixed the same problem for me. The only difference was I had a 1.9
and a 1.7 entry. I deleted the 1.9 key and my problem was fixed.
Other info:
OS: Windows 10
Visual Studio Professional 2015
C# Windows Form Application
This was on my work laptop. We have Office 2010 installed on each workstation.
Some other things I tried that DID NOT WORK were the following:
Repairing MS OFFICE
Reinstalling MS OFFICE
Downloading Microsoft Office 2010: Primary Interop Assemblies from Microsoft.
I also had several versions of the Microsoft.Office.Interop.Excel.dll on my laptop. Deleting previous versions did not fix the problem.
Glad I went to STACKOVERFLOW.COM because this place ROCKS!!!!!!
We had the same problem.
Our setup is like this :
Office 2010 : Word and Excel
but
Office 2013 : Outlook
We ran the installation program for Office 2010 and choose the repair option.
After that, all the wrong keys in the registry for Word and Excel were deleted and the problem was solved.
Had the same problem... The code that was previously running, started throwing the same exception when a new Application instance was created. To fix this:
Programs and Features, did an order by date installed and could see there were some Microsoft Office 365 updates from the same day the
code had stopped working.
For both Microsoft Office 365 -en-us and Microsoft Office 365 Pro Plus -en-us, right click Change and select Quick Fix
Tried to run my solution and it was working again.