Has anyone used Log4Net within BizTalk 2010 Orchestrations before? Recently I ported my BizTalk solution from BizTalk 2006 R2 to BizTalk 2010. The log4net I'm using is the wrapper written by Scott Colestock. After migrating to BizTalk 2010, the logs are no longer printing but still the orchestrations run without any error.
I tried to add the following to the log4net config as suggested by some (though those usage of log4net are not BizTalk context). Still it is not working. Anyone has any clue or experience in making log4net work in BizTalk 2010?
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>
Did you move to an x64 server and are you running x64 hosts? There might be something missing for your Log4net to work. See this thread.
If that might be, try run it in a x86 host and see if it makes a difference.
I know it's not an answer, but have you looked at the guide the CAT team came up with around instrumenting BizTalk? I try to use that when I can.
Related
Is BMC.ARsystem.dll version 7.1.3128.23911 supported on Windows Server 2012? Does anyone has experience with this? I was looking for a compatibility matrix or the like on their website (communities.bmc.com)
Due to urgency of the matter from my perspective, I raise it here in addition to the forums there (it's been there a while now, compared to here). Please do let me know if this is not the proper place to put these questions, and sorry in advance if this is the case.
Thanks!
I don't know if you figured this out, but we spent three days on it.... so I thought I would share it here.
We have deployed BMC.ARSystem.dll on Windows Server 2012. We are using version 7.6 and we are using it in an ASP.Net project with .NET Framework 4.5.
These were the special steps we had to take:
Set your appliction pool identity in IIS to run in a 32 bit
compatible mode. (Go to advanced Settings - Enable 32-Bi
Applications = True)
Make sure you have the correct C++ dlls on your machine. It requires the following files to be installed in the windows/syswow63 folder: msvcp71.dll, msvcr71.dll
Make sure you include all the other Remedy dll's referenced by
BMC.ARSystem in a folder where your application will know to look
for it. It has about 16 references. You can put it in your bin
folder, or in our case we specify a private path in the web.config,
like so:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="lib"/>
I hope this helps someone else to get this working quicker.
I recently acquired XMLSpy 2013 and was naturally excited to see there was a Visual Studio integration package. I'm running VS 2012, but nowhere on Altova's download page does it mention compatibility requirements/limitations.
So I followed the steps on the Altova download site (basically just run the package and you're done). Nothing changed in VS. So I decided to download the 1326 page PDF manual for XMLSpy to see if there was some extra help in there:
http://www.altova.com/documents/XMLSpyPro.pdf
On page 490, it mentions going into your VS/Common7/IDE directory and running devenv.exe /setup which I did. After that, again, nothing changed.
Has anyone had any success with getting this integration package to work? I can find almost no information by searching the web.
I actually created a support ticket with Altova for the issue as well, but thought I'd try here for some first hand experiences.
Whelp, Altova support responded to my ticket. The answer is, since Visual Studio is a 32-bit only application, XMLSpy integration will not work when running the 64-bit version of XMLSpy/XMLSpy integration package.
This is despite the fact that both a 64-bit version of XMLSpy AND a 64-bit version of the Visual Studio Integration package exist side-by-side on the download page (as of writing this answer). I have a feeling that it might only exist for the Eclipse integration.
http://www.altova.com/download/xmlspy.html
Once I installed the 32-bit versions of XMLSpy/Integration package, it all worked as promised. I hope this helps someone in the future at least.
Is it possible to debug issues with stuff like wsstracing? Or is the disassembly the best I can get?
MOSS 2007 SP2.
Try the Microsoft Public Symbol Server. If the Sharepoint symbols are not there, your next best bet would be to install debug Windows Server from an MSDN subscription and get the symbols for it from there.
The actual symbol server is at this URL. However, it is not browsable in a browser, it's useful only in WinDbg.
To answer myself: No, there aren't.
.NET Reflector now has a "Pro" version which will allow you to step through and debug just about any third party assembly including the SharePoint assemblies (with the exception of code that is obfuscated).
I actually just downloaded it today, and it looks really good! It integrates with Visual Studio, and is seamless when stepping from your own code into the SharePoint assembly's code.
http://www.red-gate.com/products/reflector/index.htm
I am writing a VS2008 add-in that connects to a remote database blah blah.
I am having a problem with the app.config in this project. When I use SubSonic in my code, it moans that is cannot find the SubSonicServer section. This is because the .config file cannot be found.
This appears to a problem with paths as the add-in is a DLL running in the context of VS2008 and the working directory is C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE.
Is there a way to get the app.config to deploy properly with the application so my add-in (and SubSonic) can find what it needs in the .config file, or is there a way to get SubSonic to work without the need for the .config?
I am very experienced in SubSonic projects now, but only winforms, web, web service, and WPF applications. This is the first time I have tried to use SubSonic in a VS2008 Add-In project. I also have AppSettings in the config file which the ConfigurationManager cannot read because it cannot see the .config file.
2AM now and brain is tired of trying to figure this one out. Hopefully there is an answer when I wake up :)
TIA
My suggestion would be to not use the app.config file and inject the parameters at runtime.
I use this approach in my Subsonic 2.2 project:
http://www.digvijay.eu/digvijay.eu/post/2008/10/31/SubSonic-Trick-Specify-connection-string-at-runtime!.aspx
You might want to have a look at the answer to this question which deals with configuration for add-ins:
How to use app.config with Visual Studio add-in?
Does anyone use the MS SharePoint Solution Generator and VSeWSS 1.2 in a multi-developer environment with source safe? We are having issues re-deploying (because it doesn't really upgrade the solution with stsadm). It keeps saying the same feature is already installed - which it is, but it should retract the feature and re-install it - which it doesn't on some machines. Something is messed up with the feature's GUID but we can't find where that might be. One dev will be able to deploy and re-deploy but then the next dev won't. Where does VSeWSS 1.2 change the GUIDs? ARG!!!
We see the nice deployment targets (upgrade, etc) in STSDev but we're reluctant to use STSDev or the other codeplex tools because they are not supported by Microsoft. We have Visual Studio 2005 but not the money to upgrade to VS 2008 to get VSeWSS 1.3 - bummer.
---UPDATE----
I think we found a bug in VSeWSS that other's have commented on: Editing the projects properties resets some feature GUIDs.
It might also be a problem with the scope of the install. How do we get a site definition to install to the FARM scope in VSeWSS 1.2?
Don't worry too much about supported by Microsoft too much. While it is a consideration, the end result of MS SharePoint Solution Generator (terrible) and VSeWSS 1.2 are still SharePoint solutions and all solutions need to contain the same xml.
Could the deployment targets for STSDev be modified to work with your VSeWSS solution? After all, the deployment targets here are just working with STSAdm and a solution file.
In order to avoid the usual "works on my machine" you should set up a build and deployment system. If you are using virtual server or ESX server it should be fairly simply, and cheap as well. You should be able to use open source software all the way if you have more man power then money.
VSeWSS 1.2 and 1.3 store the feature GUID's in files in the /PKG directory of your Visual Studio solution. If you delete these files, or check our project into Source Control without these files and check them out on another machine, you will lose your GUIDs. Sure, VSeWSS will recreate the missing files for you, but it will do so with new GUIDs and new feature names.
A common requirement is to add the /PKG directory to your Visual Studio 2008 project and get it into source control.
You can read more about the files in the /PKG directory in the Release Notes for VSeWSS 1.3 here.
PS: We did some improvements to the Solution Generator in VSeWSS 1.3, but it wont generate a 100% perfect solution for you.