This is a function I wrote to receive a transfer order. The code will receive into the default receiving location as defined when the transfer order was placed. I found other code snippets for creating a transfer order but none to receive.
<span class="kwrd">static</span> <span class="kwrd">void</span> receiveTransferOrderToDefaultLocation(str 20 transferId)
itpt.ParmId = RunBaseMultiParm::getSysParmId();
itpt.TransferId = transferId;
itpt.UpdateType = InventTransferUpdateType::Receive;
itpt.PrintTransferReceipt = NoYes::No;
itpt.ReceiveUpdateQty = InventTransferReceiveUpdateQty::All;
itpt.EditLines = NoYes::Yes;
itpt.ExplodeLines = NoYes::Yes;
itpt.InventDimFixedReceiveList = 245; <span class="rem">// See note below on how to compute this.</span>
itur = InventTransferUpdReceive::newParmBuffer(itpt);
<span class="rem"> #DEFINE.INVENTLOCATIONID_IDX(0)</span>
<span class="rem">> #DEFINE.BATCH_IDX(1)</span>
<span class="rem">> #DEFINE.LOCATION_IDX(2)</span>
<span class="rem">> #DEFINE.PALLET_IDX(3)</span>
<span class="rem">> #DEFINE.SERIALID_IDX(4)</span>
<span class="rem">> #DEFINE.CONFIGID_IDX(5)</span>
<span class="rem">> #DEFINE.INVENTSIZEID_IDX(6)</span>
<span class="rem">> #DEFINE.INVENTCOLORID_IDX(7)</span>
<span class="rem">binary: 11110101</span>
<span class="rem">decimal: 245</span>
So I use http://di.fm and Shoutcast to stream music while I write code. I have always used the Open URL function of Windows Media Player to start streaming. I did not bother to write an app for this because I have been so busy. Luckily someone else already has 😉
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized attribute ‘multipleSiteBindingsEnabled’. Note that attribute names are case-sensitive.
Line 105: -->
Line 106: <system.serviceModel>
Line 107: <serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
Line 108: <services>
Line 109: <service behaviorConfiguration="RFID.Server.WCF.Service1Behavior" <br />name="RFID.Server.WCF.Service1">
Source File: C:\inetpub\web\services.test.\RFIDServer\web.config Line: 107
Microsoft .NET Framework Version:4.0.21006; ASP.NET Version:4.0.21006.1
Received the above error message when executing a WCF service on a test server. The WCF service was compiled with .NET 4.0 RC and the test server only had .NET 4.0 Beta 2 installed. The fix was easy. Install .NET 4.0 RC full runtime on the test server and it worked.
Update: Good news! Microsoft has verified that in the RTM build this bug has been resolved. Much thanks to Go-Live support for taking this issue on and validating the issue is resolved.
From VS2010 Beta 2 to VS2010 RC we lost the ability to choose the data type ObservableCollection when configuring a service reference in a Silverlight application. I am going to use this blog post to chronicle my discussion with Microsoft Go-Live support about this functionality change.
This may be a user education issue but the difference is significant and affects all of the production projects we currently have for Visual Studio 2010 Beta 2.
Today we upgraded 3 of our developer machines from Visual Studio 2010 Beta 2 to the Visual Studio 2010 RC. In beta 2 when adding a Service Reference to a Silverlight 3 application we were given the option to choose a collection type of: System.Collections.ObjectModel.ObservableCollection in the Collection type drop down box.
Now in the release candidate we are no longer given the option to choose ObservableCollection. Instead the dropdown offers ( Custom ), Array, Generic List (and another). This presents us with several issues. Existing Beta 2 code can no longer update service references without converting all return types from Array or List<> to an ObservableCollection.
For Silverlight applications this is pretty major as we pass Generic Lists from our WCF service and heavily relied on the ability for the WCF Proxy class to deserialize the list into an ObservableCollection since these are bindable directly to our Silverlight grids.
Please advise. Is this the way this will work in production or is it possible to patch the RC to provide this functionality once again.
Please feel free to call me tomorrow ( 2/10/2010 ) from 9AM EST to 8PM EST to discuss if you need more information. It has been a while since I used Visual Studio 2008, but I am pretty sure that VS 2008 also provided the ObservableCollection collection type option when configuring a service reference.
To verify the Beta 2 vs. RC functionality difference I tested this against the same exact WCF service in both B2 and RC.
Blankenburg posted this on Friday. Very cool thing and I never even knew about it. Often times I am coding and am inserting a line of code above some existing code. Many times the two are related and I need to see the line below but Intellisense covered it up. Drat. Press the left control key and it will get out of your way!
This work around did not work for me. I have a solution with several projects. One of them is a WPF application that uses a Telerik third party control for the DataGrid. Yesterday everything worked fine and this morning I came in to work and I get the error:
Error 3 Unknown build error, ‘Cannot resolve dependency to assembly ‘Telerik.Windows.Controls, Version=2009.3.1314.35, Culture=neutral, PublicKeyToken=5803cfa389c90ce7’ because it has not been preloaded. When using the ReflectionOnly APIs, dependent assemblies must be pre-loaded or loaded on demand through the ReflectionOnlyAssemblyResolve event. Line 12 Position 10.’ D:\Projects\RFID\Source\RFID\Client\RFID.Client.UI\View\IdleView.xaml 12 10 RFID.Client.UI
No checkouts or get latest was performed. Restarted VS2010 did not work.
In my case the work around was to add the Telerik.Windows.Controls assembly to the project references manually. This should have been done by the drag/drop of the Telerik control to the design surface but it did not. Other issues were reported on connect.microsoft.com explaining that assemblies with a 2nd degree of separation which are not normally required to be directly referenced are now needed in VS2010 for whatever reason.