Any CPU platform and X86 Platform - vb.net

I am really confused about target platform. For best results, to make my application run on any CPU, what target platform should be used. I tried Any CPU but my application does not run on Windows 7 with Access 2010 installed. It returns an error
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine
Someone told me to avoid this error, change platform to X86. But I am unable to change that too. Dropdown menu contains only Any CPU.
What to do?
Thanks

In your connection string, try replacing
Provider=Microsoft.Jet.OLEDB.4.0
with
Provider=Microsoft.ACE.OLEDB.12.0;

In order to get new platforms, you can go into configuration manager and add a new one, but I thought x86 was one of the default ones provided. Here's a link for you. Quoted here in case MS moves their stuff around yet again.
Here are common procedures for creating and managing solution build
configurations:
To create a Solution Build Configuration
Open the Configuration Manager dialog box.
On the Active Solution Configurationdrop-down list, choose New.
The New Solution Configuration dialog box opens.
Type a name for the new solution build configuration in the Name text
box.
To use the same settings as those specified for another solution build
configuration, choose one from the drop-down list for the Copy
settings from textbox.
If you want to create one or more project configurations at the same
time, select the Create new project configurations check box.
To rename a Solution Build Configuration
Open the Configuration Manager dialog box.
On the Active Solution Configuration drop-down list, choose Edit.
The Edit Solution Configurations dialog box opens.
Select the solution build configuration name you want to change.
Select Rename, then type a new name for the configuration.
To select and edit a Solution Build Configuration
Open the Configuration Manager dialog box.
Select the desired solution build configuration from the Active
Solution Configuration drop-down menu at the top of the dialog box.
The Project Contexts panes display the properties of the active
solution build configuration.
Select any project available in the solution.
Select the desired project Configuration and Platform. Together, these
two settings specify the project configuration to be used.
If the project is to be included when you build this solution build
configuration, select the Build check box.

Related

What is it called when an app set some configurations at build time?

A common pattern used to build applications/software (web, mobile, desktop) is to have multiple build configs like Dev, Stage and Production. Each one of these configs may overwrite multiple variables like the base url of a web service that is consumed by the application. These configs may be stored in multiple ways (.env file, a JSON config file, etc).
I was looking for a name for this pattern/practice and how to implement it on a VB.NET application. Most close thing I was able to found is using the app.config file to store app settings but this is missing the multiple environments part. I'm having some trouble looking for solutions since I don't know the proper term for this practice.
There's a Solution Configurations drop-down on the main toolbar. You would have already used it to select Debug or Release. You can open the Configuration Manager from there to create new build configurations.
You can then control what happens during the build process of a project for a particular configuration on the Build page of the project properties. You can also perform actions using build events, which you configure on the Build Events page of the project properties. Here's an example of a pre-build event commandline that I use to automatically select the appropriate config file for NLog:
IF EXIST "$(ProjectDir)nlog.$(ConfigurationName).config" XCOPY "$(ProjectDir)nlog.$(ConfigurationName).config" "$(ProjectDir)nlog.config" /Y

Can I commit and share VM options in IntelliJ?

To execute my application, or run or debug unit tests, I need to enable various VM options, include -javaagent:<aspectjweaver-path> or -Djava.library.path=<some native lib path>
I can see how to change these configurations manually in IntelliJ IDEA under "Edit Configurations..."
What, if anything, do I need to check in to my VCS to share these settings with other members of my team, and ensure they pick them up automatically whenever someone changes them in the VCS?
Alternatively is there a way to set these automatically in IntelliJ without even touching the edit configurations? Especially the aspectjweaver. When I build/test my project from the command line using maven this is all handled for me by specifying argLine arguments to the surefire plugin, but IntelliJ doesn't respect these settings. Perhaps there are alternative plugins that can help me out?
First, you need to share your run configuration. It's simply done by checking the Share box right to the configuration name in the run configuration dialog:
Your run configuration will then be saved to .idea/runConfiguration (or whatever your settings folder name is).
From Jetbrains Web Help:
If this check box is selected, the run/debug configurations become available to the other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml.
This field does not appear for the default run/debug configurations.

libc.dll files is required but can not find it

I am trying to publish my application using installShield utility. Every thing works fine but it gives warning that it asks for two files:
libc.dll
Flash32_11_7_700_224.ocx
Those two files are prerequisite according to the package but I could not find them.
I tried to search in the web for those two files with no luck.
Can any one help in this?
Explanation of Error
This error can be encountered in Flexera's InstallShield. The specific error is:
ISEXP : warning -6248: Could not find dependent file <dependent file>,
or one of its dependencies of component <component>
The official troubleshooting information from helpnet.installshield.com did not help me, but it says to:
Use the "Build Tables & Refresh Files" option to build the release
if the release location is in <ISProjectDataFolder>
or <ISProjectFolder>. For more information, see "How the Run time
Locates Assemblies", available in the .NET Framework SDK help or on MSDN.
Workaround
If the application works fine, and you just want to get rid of the warnings, you can follow this Stack Overflow Q&A.
(InstallShield, Installation Designer, Left Panel) Specify Application Data > Files
(Destination computer's files panel) Right click primary output > Dependencies from scan at build... > Uncheck dependencies you do not want
The above picture from the Stack Overflow answerer #Tom Wilson shows what you should see. Note that primary output was the central .exe of my project. When I used this technique on my primary output, the other components in my project were also fixed.
Resolution
If this problem is crashing your application, and not just an annoying warning...
In the case of libc.dll, I would direct you to add Redistributables to your project.
(InstallShield, Installation Designer, Left Panel) Specify Application Data > Redistributables
For instance, I use Microsoft .NET Framework 4.7.1 Full.
I believe this solution will work for libc.dll, but cannot verify. I base this on reading support.microsoft.com, which I think implies libc.dll is contained in C Run-Time (CRT), which I would also believe is part of the .NET Framework.
In the case of flash32_11_7_700_224.ocx, I would direct you to System Software Requirements. This ocx is installed with many Adobe products. You may want to prompt the user that they need to install this, at the time software installation.
(InstallShield, Installation Designer, Left Panel) Define Setup Requirements and Actions > Requirements
(Central Panel) System Software Requirements > Right click > Create New Launch Condition (System Search Wizard)
Follow the wizard there to block installment if it does not exist, or use one of the premade requirements if that helps your case. Tip: remember to supply a link to Adobe in your prompt, so your end-user can quickly download it!

Register App for Symbolication in XCode Profiler

I'm trying to run XCode's time profiler on my app that is running on my device, but the symbol names show up like 0x2fe26643 instead of [MyClass myMethod]. I realize I need to re-symbolicate the app, but I don't know how.
A few answers like this and this say to press "Re-Symbolicate", find your binary in the list, then press "Locate" to find the dSYM manually. My app is not in the list called dSYM Locations:
How I can get my results symbolicated?
UPDATE: I posted a YouTube clip of what it looks like when I try to re-symbolicate: http://www.youtube.com/watch?v=CcLGRNkmako
I was having this same problem when trying to profile my app on device (worked fine in simulator). When trying to re-symbolicate, my app binary was not showing up at all under the "dSYM Locations" dialog list, so I wasn't able to select it and then use the Locate button to associate the appropriate dSYM as other answers have suggested.
I was able to get symbolication back in the device profiling by going to Edit Scheme in Xcode and changing the Profile build to Debug instead of Release.
Here is what I did to enable profiling, without switching to debug mode. This is for Xcode 4.5.1
Create a new "Profile" build configuration, based on the existing
"Release" configuration: Select the project in the project navigator
to open the project editor. Select the project in the project editor
and click the Info button. Expand the Configurations section in the
Info pane and click the Add (+) button at the bottom of the section.
Select the existing "Release" configuration from the pop-up menu as
a starting point for the new configuration. Select the name of the
copy and type "Profile". See more in the Xcode User Guide.
Set the Code Signing Identity of the "Profile" configuration to
"iPhone Developer" (or the same as your "Debug" configuration):
Click the Build Settings button to display the build settings for
the project. To change the build settings in the new configuration
for all the targets in the project, edit them at the project level.
To change the build settings for an individual target, select that
target. If you edit them at the project level, make sure that you
double-check the target level afterwards: target settings override
project settings. The Code Signing Identity is in the "Code Signing"
section.
Make sure that the "Generate Debug Symbols" setting is YES for
the "Profile" configuration. It was already YES in my case.
Set your new "Profile" configuration to be used by the "Profile"
scheme: Select "Product->Edit Scheme" from the menu, select the
"Profile appname.app" tab at the left, and then select the "Profile"
under "Build Configuration".
In your appname.entitlements file set the "get-task-allow"
property to YES.
Press the ALT key, and select "Product->Clean Build Folder" from
the menu.
Now select "Product->Profile" from the menu, and you should be
good to go.
All kinds of strange things can happen if you don't do all of this. I have had no symbols show up at all, or only library symbols show up. I have had symbols only showing up if you first do a debug build, and then profile afterwards (which means the symbols are probably incorrectly taken from the debug build). I have had the profiler complaining about UUID mismatch, and I have had the infamous "Entitlements do not match" error (see more on that here).
They mean to press the "Locate" button and then find your app in ~/Library/Developer/Xcode/DerivedData. I've found, however, that the following seems to work:
Preferences > Search Paths
Add ~/Library/Developer/Xcode/DerivedData (I actually have this as /Users/rnapier/..., so I'm not certain if ~ works)
This still doesn't always auto-symbolicate for me. But it lets me use File>Re-Symbolicate Document, and then just hit the "Symbolicate" button and it's been working for me. The fact that this doesn't work "out of the box" is insane....
I recommend duping radr://10158512 (which is itself a duplicate of 10015727, but that one isn't in openradar).
This also depends on where XCode is putting your build. You can select "MyCoolApp.app" in the XCode project organizer, right or control-click for "Show in Finder". Not all project settings will put it in DerivedData (several different project settings can conspire to put it in different locations). Now that you've found where XCode is depositing your builds, you can try adding it to Instruments from there using the steps previously outlined. When the File dialog comes up from clicking "Locate...", you can just drop the .app from the Finder on the File dialog and it will go to that directory.
If you change the code signing identity for your "Release" build configuration from "Automatic Profile Selector: iPhone Distribution" to "Automatic Profile Selector: iPhone Development" (emphasis mine) then your app's binary will be listed in Instrument's Re-Symbolicate sheet and you can point it at your Derived Data folder.
No success with above mentioned. What worked for me with Xcode 5:
Get location of your product as described in quellish's answer. Ex.
/Users/ME/Library/Developer/Xcode/DerivedData/Build/Products/Debug-iphoneos
/Users/ME/Library/Developer/Xcode/DerivedData/Build/Products/Release-iphoneos
Open Instruments Preferences and add the location(s) in "dSYMs And Paths".

Making SSDT just generate a SQL script (and not deploy a database)

Having recently upgraded to SSDT 2012 I seem to be missing the option to just generate a T-SQL script instead of deploying the database to a server somewhere.
To be more accurate the predecessor to SSDT used to set the Deploy action to 'Generate script', but I cannot locate that option anywhere in the new version.
Is it possible?
To generate a script from an offline data project in SSDT rather than deploy to a target database, configure the project settings as shown below
You may want to look at the SQLPackage command line. You can set the options there to use an action of "script" and specify an outputfile name to generate scripts instead of publishing the database. You can also do that through a batch file so it will generate a script every time. You still need to provide a source project and target database, though. The reference for SQLPackage can be found here: http://msdn.microsoft.com/en-us/library/hh550080%28v=VS.103%29.aspx
Yes, it is possible.
Is you select Build > Publish ProjectName... from the menu bar, a dialog window pops-up with publishing options – there's a Generate Script button at the bottom of the dialog window.
I also had a problem where the SSDT project would attempt to deploy changes when the project was run.
In the project properties, choose the "Debug" tab. Change the Start Action to "None". That will prevent it from trying to deploy at that time.